Gang, I have made a first cut to migrate away from Maven and onto Gradle. Gradle comes with a pretty nifty task that creates batch/shell scripts to auto-bootstrap Gradle, so that subsequent developers don't need to bother with installing Gradle itself.
In essence, Gradle is based on the Groovy programming language, so the build scripts are really Groovy code, with an 'implicit' object model to make that makes such scripts fairly condensed. Instead of trying to invent everything from scratch, I started off with the Hibernate build scripts and modified to our need. This is still work in progress, but up to now it compiles the sources, run the tests and package jar files into target/libs. I have chosen to keep the Qi4j 'version' outside the build definition itself, and must be supplied externally during the release itself, and I will add a 'snapshot' task that will generate timestamped versions for nightly builds and such. If no version is supplied a "dev" version is used. The code for release management from Hibernate is still in there, but I have not checked it at all, and will tackle that in due time. Ohhh... This is all in qi4j-core only at the moment, as I want to get this working nicely before replicating it across the repositories. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
