Maven2 builds
Hi, unless anybody yells I should stop I'm going to be more pragmatic about Maven 2 builds. Several projects depend on BCEL and if we are unable to build BCEL from source those projects no longer benefit from Gump's early warning system. I've modified trunk so that it doesn't pass --offline to mvn any longer and with some help by Brett managed to get BCEL building on helios. I intend to install Maven 2 on vmgump and start adding Maven2 builds. At least for those projects that have dependents which are not built by Maven2; not too sure what to do with leaf projects since for them we'd just provide another nightly build system. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 builds
On May 2, 2007, at 8:38 AM, Stefan Bodewig wrote: I've modified trunk so that it doesn't pass --offline to mvn any longer and with some help by Brett managed to get BCEL building on helios. I intend to install Maven 2 on vmgump and start adding Maven2 builds. I have a Maven 2 on Clarus (2.0.5, will upgrade if necessary), and I think it tries to build Maven2 projects. Clarus is running gump trunk. Anything else I need to do? S. -- [EMAIL PROTECTED] http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF smime.p7s Description: S/MIME cryptographic signature
Re: Maven2 builds
On Wed, 2 May 2007, Sander Temme [EMAIL PROTECTED] wrote: On May 2, 2007, at 8:38 AM, Stefan Bodewig wrote: I've modified trunk so that it doesn't pass --offline to mvn any longer and with some help by Brett managed to get BCEL building on helios. I intend to install Maven 2 on vmgump and start adding Maven2 builds. I have a Maven 2 on Clarus (2.0.5, will upgrade if necessary), and I think it tries to build Maven2 projects. Clarus is running gump trunk. Anything else I need to do? Only if you get a build error when building BCEL ... which you do. You must remove ~/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/ since some attempt to run mvn --offline has left corrupt metadata in it (known bug in mvn). After that the build should succeed, but the jar file may be wrong (Brett and I tried to fix that, but don't know whether it worked, yet). Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
