I don't think is a problem in either maven or surefire plugin. Else the surefire is behaving differently.
It looks like now, when surefire forks the jvm, will not take all the system properties from the parent jvm. That's why you should pass whatever system properties you want for the tests, using argLine. So, both these should work mvn2.1 -Dsystem.test.property=test test -DforkMode=never or mvn2.1 test -DargLine="-Dsystem.test.property=test" , costin -- View this message in context: http://www.nabble.com/maven-2.1.0-not-passing-on-system-properties-to-java-virtual-machine-tp23133501p23383667.html Sent from the Maven - Users mailing list archive at Nabble.com.
