Skip to content

Proof of concept for a new tech stack.. Gradle for builds, jboss with automated installation / deployment, spring + distributed transactions..

Notifications You must be signed in to change notification settings

larshvile/jboss-spring-tx

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

54 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Gradle issues:
---------------------------------------------
- No way to run 'offline' builds - http://issues.gradle.org/browse/GRADLE-320
    could possibly be fixed by an env variable that simply disables the remote repository??
- Update policy for maven SNAPSHOT dependencies. Supposed to work out of the box, but should be tested
    http://gradle.1045684.n5.nabble.com/Snapshot-dependencies-not-updated-td1433032.html
    http://issues.gradle.org/browse/GRADLE-629
- Automatic dependency resolution between Jenkins jobs not possible in the current Gradle plugin.

- deb installers?.. https://github.com/sgo/ubuntu-packager-plugin

TODO
---------------------------------------------

- loads of TODOs in the build scripts...

- proper jboss installation w/config
    - snowdrop should probably be bundled with the dist, since it requires a reload...

- spring/hibernate dependencies...
    'org.hibernate': [], // TODO no longer a 'pure' spring bundle?? maybe it would be easier to have a 'fat' jee-libraries module? .. how does optional="true" work?

- jboss has loads of shared libraries as modules.. need to stay in sync with these...
    "hibernate" ->
        <module name="asm.asm"/>
        <module name="javax.api"/>
        <module name="javax.persistence.api"/>
        <module name="javax.transaction.api"/>
        <module name="javax.validation.api"/>
        <module name="org.antlr"/>
        <module name="org.apache.ant"/>
        <module name="org.apache.commons.collections"/>
        <module name="org.dom4j"/>
        <module name="org.infinispan"/>
        <module name="org.javassist"/>
        <module name="org.jboss.as.jpa.hibernate"  slot="4"/>
        <module name="org.jboss.logging"/>
        <module name="org.hibernate.envers" services="import" optional = "true"/>


- deployments w/dependencies
    backend = .ear + libs & .spring ?
    web = .war / .ear + .war?

- deployment scripts must be idempotent? -- not really safe or sane to delete/redeploy every time? What about temp data dirs etc?

- jboss-admin.sh doesn't return error codes?

- classcycle reports, gradle/gradle/classcycle.gradle

- codenarc kicks ass as well

- findbugs/pmd etc have been included as standard plugins..

About

Proof of concept for a new tech stack.. Gradle for builds, jboss with automated installation / deployment, spring + distributed transactions..

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published