From: James Macgill <jrm33@ps...> - 2004-02-29 22:14:44
I've just committed the first version of a binary build goal to cvs, it
doesn't do much yet but it is a start.
To use it you need to type
maven -Drelease.version=B2 buildBinRelease
This will create a zip archive with the compiled jars and a lib folder
containing the 3rd party jars. As it stands only some of the modules are
configured for release but there is not much involved in adding a new one.
1) Add maven.module.stable=true property to the modules build.properties file
2) For each dependency that can and should be distributed with the binary
release modify its entry in the modules project.xml file so that it looks
like something like this one for JTS.
Please be careful not to add this to any jars which, for license reasons,
we can not re-distribute.
Try calling the buildBinRelease and check the releaseReport-version.txt to
make sure your module made it OK and then check the binRelease/lib folder
to make sure any deps also made it.
There is clearly more to do - generation of readme/changelogs, inclusion of
licenses, creation of maga jar etc. So we may have to use a combination of
this goal and hand rolling to get a release out tomorrow.
Let me know if it works/fails for you.
p.s. I'm traveling again tomorrow (back to the US this time) so I'm afraid
I'm going to miss the IRC again this week :(