geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Build changes coming...
Date Thu, 02 Sep 2004 00:21:37 GMT
Depending on how ambitious you are feeling you might consider using 
multiproject instead of our homegrown solution.  Being able to select 
the modules and types easily is nice but I no longer think it is worth 
maintaining the jelly code to do it.  As I pointed out a few weeks ago 
it is already possible to build everything together using multiproject.

I haven't tried building the site using multiproject.

+1 on all the suggested changes

We also need to separate each modules' deployment code into a separate 
module, but this will probably be easier after your changes.

david jencks

On Sep 1, 2004, at 5:12 PM, Dain Sundstrom wrote:

> David Blevins and are working on simplifying the build so we can 
> easily produce daily builds.  The biggest change is the consolidation 
> of dependency version numbers into etc/version-info.ent file.  This 
> makes doing a build across geronimo, openejb, tranql and activemq much 
> easier, and makes upgrading individual libraries simple.
> There are a few other minor things on the list:
> * Finally moving the geronimo-spec/schema module to 
> modules/spec-schema, so we can remove the spec tree from our normal 
> build since it is slow
> * Add ability to easily just build without assembly since assembly is 
> so slow
> * Change build to not fork most tests since is is slow
> * Add a -java-src artifact to the build that contains just the java 
> source for each module (makes debugger setup easier)
> If there are any other (minor) changes, you want me to make while at 
> this, let us know, and if you don't like these changes please speak 
> up.
> -dain
> --
> Dain Sundstrom
> Chief Architect
> Gluecode Software
> 310.536.8355, ext. 26

View raw message