You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2008/04/28 23:05:46 UTC
[jira] Created: (SUREFIRE-491) All system properties from Maven
process are copied to forked Surefire process
All system properties from Maven process are copied to forked Surefire process
------------------------------------------------------------------------------
Key: SUREFIRE-491
URL: http://jira.codehaus.org/browse/SUREFIRE-491
Project: Maven Surefire
Issue Type: Bug
Components: process forking
Affects Versions: 2.5
Reporter: Dan Fabulich
Run a Surefire test with a different JVM using the -Djvm argument. For example, run the test with JDK 1.4 while running Maven with a 1.5 or 1.6 JVM.
Examine the XML file in target/surefire-reports corresponding to your test. The java.* properties will match the parent process, not the forked process. For example, <property name="java.version" value="1.6.0_02"/>.
--
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
[jira] Updated: (SUREFIRE-491) All system properties from Maven
process are copied to forked Surefire process
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich updated SUREFIRE-491:
----------------------------------
Fix Version/s: (was: 2.5)
2.4.3
> All system properties from Maven process are copied to forked Surefire process
> ------------------------------------------------------------------------------
>
> Key: SUREFIRE-491
> URL: http://jira.codehaus.org/browse/SUREFIRE-491
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4.3
> Reporter: Dan Fabulich
> Fix For: 2.4.3
>
>
> Run a Surefire test with a different JVM using the -Djvm argument. For example, run the test with JDK 1.4 while running Maven with a 1.5 or 1.6 JVM.
> Examine the XML file in target/surefire-reports corresponding to your test. The java.* properties will match the parent process, not the forked process. For example, <property name="java.version" value="1.6.0_02"/>.
--
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
[jira] Commented: (SUREFIRE-491) All system properties from Maven
process are copied to forked Surefire process
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132897#action_132897 ]
Dan Fabulich commented on SUREFIRE-491:
---------------------------------------
This is happening due to the fix for SUREFIRE-121. I was afraid when I did this that it was risky:
http://www.nabble.com/passing-system-properties-to-forked-test-td13947630.html
I even included a comment in the code: [Is this wise?|http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java?r1=598217&r2=598216&pathrev=598217]
In hindsight, it was not wise; the initial implementation broke the embedder. Milos fixed that later, but it's still doing the wrong thing from the command line.
I'm not exactly sure how to fix this without breaking the fix available in SUREFIRE-121...?
> All system properties from Maven process are copied to forked Surefire process
> ------------------------------------------------------------------------------
>
> Key: SUREFIRE-491
> URL: http://jira.codehaus.org/browse/SUREFIRE-491
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.5
> Reporter: Dan Fabulich
>
> Run a Surefire test with a different JVM using the -Djvm argument. For example, run the test with JDK 1.4 while running Maven with a 1.5 or 1.6 JVM.
> Examine the XML file in target/surefire-reports corresponding to your test. The java.* properties will match the parent process, not the forked process. For example, <property name="java.version" value="1.6.0_02"/>.
--
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
[jira] Closed: (SUREFIRE-491) All system properties from Maven
process are copied to forked Surefire process
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-491.
---------------------------------
Resolution: Fixed
Fixed revision 652773.
> All system properties from Maven process are copied to forked Surefire process
> ------------------------------------------------------------------------------
>
> Key: SUREFIRE-491
> URL: http://jira.codehaus.org/browse/SUREFIRE-491
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4.3
> Reporter: Dan Fabulich
> Fix For: 2.4.3
>
>
> Run a Surefire test with a different JVM using the -Djvm argument. For example, run the test with JDK 1.4 while running Maven with a 1.5 or 1.6 JVM.
> Examine the XML file in target/surefire-reports corresponding to your test. The java.* properties will match the parent process, not the forked process. For example, <property name="java.version" value="1.6.0_02"/>.
--
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
[jira] Updated: (SUREFIRE-491) All system properties from Maven
process are copied to forked Surefire process
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich updated SUREFIRE-491:
----------------------------------
Affects Version/s: (was: 2.5)
2.4.3
Fix Version/s: 2.5
> All system properties from Maven process are copied to forked Surefire process
> ------------------------------------------------------------------------------
>
> Key: SUREFIRE-491
> URL: http://jira.codehaus.org/browse/SUREFIRE-491
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4.3
> Reporter: Dan Fabulich
> Fix For: 2.5
>
>
> Run a Surefire test with a different JVM using the -Djvm argument. For example, run the test with JDK 1.4 while running Maven with a 1.5 or 1.6 JVM.
> Examine the XML file in target/surefire-reports corresponding to your test. The java.* properties will match the parent process, not the forked process. For example, <property name="java.version" value="1.6.0_02"/>.
--
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