[
http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160349#action_160349
]
Chico Charlesworth commented on SUREFIRE-121:
---------------------------------------------
This bug is preventing us from using 2.4.3, as we're running our tests behind a
proxy, i.e. ('mvn test -Dhttp.proxyHost=<proxyHost>
-Dhttp.proxyPort=<proxyPort>), and the system properties http.proxyHost and
http.proxyPort are being passed in as null. With 2.4.2, it works fine.
Can someone say when we can expect this to be resolved? Or if there's another
workaround for the time being?
> 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: Critical
> Fix For: Future
>
>
> 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
