[
http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint reopened SUREFIRE-121:
-----------------------------------
This seriously breaks embedded usage. See this email sent to mevenide's mailing
list:
----
It looks like, although my tests are configured to use either
forkMode=once or forkMode=perTest, Mevenide and/or the
maven-surefire-plugin in 2.4 either do not fork or (most probably) start
these new JVMs by explicitly (and incorrectly) passing all the system
properties and property values of the currently running JVM (i.e. the
JVM running the Netbeans IDE).
This means these system properties have "interesting" values when the
JUnit test code is running, like e.g.:
javax.xml.parsers.DocumentBuilderFactory=org.netbeans.core.startup.DOMFactoryImpl
javax.xml.parsers.SAXParserFactory=org.netbeans.core.startup.SAXFactoryImpl
As these NetBeans factory classes are not available from my project's
Meven test classpath, all my XML-related tests do now fail.
In addition, I get a message about a missing Logger configuration class:
Logging configuration class "org.netbeans.core.startup.TopLogging" failed
java.lang.ClassNotFoundException: org.netbeans.core.startup.TopLogging
--
> System properties set on the command line get clobbered
> -------------------------------------------------------
>
> Key: SUREFIRE-121
> URL: http://jira.codehaus.org/browse/SUREFIRE-121
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Environment: Linux, Maven 2.0.4, Sun JDK 1.5U5, bash 3.0
> Reporter: Brenton Leanhardt
> Priority: Minor
> Fix For: 2.x
>
>
> Some system properties get clobbered if you set them on the command line. For
> example,
> mvn clean test -Dtest=LoginTest -Dselenium.user=test32
> The 'test' system property will work, but the 'selenium.user' property will
> be null at runtime. I have tried:
> * hard coding the system property in the unit test, this worked fine.
> * setting the system properties in the pom file, this worked fine also.
> * tried an older version of the surefire plugin, this worked fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
