Re: [continuum] BUILD FAILURE: Commons Configuration

Junit tests are forked by Maven, so Continuum can't really set that property itself. I think it's best for the project to configure it if it requires AWT but doesn't require a display so that anyone that builds it on a headless machine doesn't need to do so. I expect that setting -Djava.awt.headle

Re: [continuum] BUILD FAILURE: Commons Configuration

Maybe Continuum should be running headless, as other projects might also try to use awt code in the future. Michiel On 8/29/07, Jörg Schaible <[EMAIL PROTECTED]> wrote: > Hi Oliver, > > Oliver Heger wrote on Tuesday, August 28, 2007 6:32 PM: > > > Henri Yandell wrote: > >> We can change CI to use

RE: [continuum] BUILD FAILURE: Commons Configuration

Hi Oliver, Oliver Heger wrote on Tuesday, August 28, 2007 6:32 PM: > Henri Yandell wrote: >> We can change CI to use a JDK 1.6 if that's what Configuration's >> target is. > > This doesn't seem to be the problem. We get errors like the > one below. > Is there anything wrong with the JDK on the

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This

Re: [continuum] BUILD FAILURE: Commons Configuration

Henri Yandell wrote: We can change CI to use a JDK 1.6 if that's what Configuration's target is. This doesn't seem to be the problem. We get errors like the one below. Is there anything wrong with the JDK on the build machine? Oliver testGetConfiguration(org.apache.commons.configuration.Tes

[continuum] BUILD FAILURE: Commons Configuration

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=2781&projectId=161 Build statistics: State: Failed Previous State: Failed Started at: Tue 28 Aug 2007 09:30:22 -0700 Finished at: Tue 28 Aug 2007 09:31:12 -0700 Total time: 50s Build Trigger: Schedule Build Num

Re: [continuum] BUILD FAILURE: Commons Configuration

We can change CI to use a JDK 1.6 if that's what Configuration's target is. On 8/28/07, Oliver Heger <[EMAIL PROTECTED]> wrote: > Just an update: the tests should now run on a JDK 1.6. I was able to get > rid of these dependencies on static fields. I also applied most of the > improvements to the

Re: [continuum] BUILD FAILURE: Commons Configuration

Just an update: the tests should now run on a JDK 1.6. I was able to get rid of these dependencies on static fields. I also applied most of the improvements to the pom.xml Michiel suggested (thanks again). However I doubt that CI will be impressed by these changes... Oliver Oliver Heger wrote

RE: [EMAIL PROTECTED]: Project commons-id (in module commons-sandbox) failed

Stefan Bodewig wrote on Monday, August 27, 2007 9:53 PM: > On Mon, 27 Aug 2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > >> I had a look at this and found these dependencies: >> >> >> >> >> >> >> >> >> >> But if I read the descriptor right, it runs 'maven

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. Th

[EMAIL PROTECTED]: Project commons-id (in module commons-sandbox) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-id has an issue affecting its community integration. This issue affects 1