Have you locked down the version of surefire you are using in your pom? if you have not locked it down, then you will be picking up a newer version of surefire with 2.1.0.
AFAIK, a newer version of surefire has issues passing system properties to the forked process. in any case you should always lock down the versions of plugins that you are using or else your build is not fully reproducible -Stephen 2009/4/20 edward eric pedersson <[email protected]>: > Hi > > We use the command line to pass on system properties to the java > virtual machine when running our Hudson builds on a Linux box. It used > to work quite well in 2.0.9 by since we upgraded to 2.1.0 it has > stopped working altogether. The system properties just never make it > to the java virtual machine. > > I have created a small test project and indeed it does not work at > all. I have attached it in case you want to give it a go. [it got > blocked so sending without attachment] > > This should work just fine with maven 2.0.9 > > mvn2.0.9 -Dsystem.test.property=test test > > But this will fail > > mvn2.1 -Dsystem.test.property=test test > > The java code simply does this > > assertTrue( System.getProperty("system.test.property") != null); > > > Any thoughts > > -- > > > -- e > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
