You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason Voegele (JIRA)" <ji...@codehaus.org> on 2008/02/28 15:22:28 UTC
[jira] Created: (SUREFIRE-461) -Xbootclasspath specified in
not passed to forked JVM
-Xbootclasspath specified in <argLine> not passed to forked JVM
---------------------------------------------------------------
Key: SUREFIRE-461
URL: http://jira.codehaus.org/browse/SUREFIRE-461
Project: Maven Surefire
Issue Type: Bug
Components: process forking
Affects Versions: 2.4.2, 2.4.1, 2.4
Reporter: Jason Voegele
Attachments: surefire-argline-bug.tar.gz
The 2.4.x versions of maven-surefire-plugin do not propagate the bootclasspath to the forked JVM that executes the tests.
I have attached a sample project that demonstrates this problem. The sample application has a test case that verifies that the -Xbootclasspath parameter given in the <argLine> of the POM is properly passed to the JVM running the tests, but the test fails when using 2.4.x versions.
If you modify the POM to use 2.3 version instead of 2.4.2, the tests pass.
--
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-461) -Xbootclasspath specified in
not passed to forked JVM
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-461.
---------------------------------
Resolution: Duplicate
Yes, I can reproduce your test failure. In fact, I think this is just a special case of SUREFIRE-491. With that said, I believe that the boot class path *is* being modified, you just can't see it in Java system properties.
> -Xbootclasspath specified in <argLine> not passed to forked JVM
> ---------------------------------------------------------------
>
> Key: SUREFIRE-461
> URL: http://jira.codehaus.org/browse/SUREFIRE-461
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4, 2.4.1, 2.4.2
> Reporter: Jason Voegele
> Attachments: surefire-argline-bug.tar.gz
>
>
> The 2.4.x versions of maven-surefire-plugin do not propagate the bootclasspath to the forked JVM that executes the tests.
> I have attached a sample project that demonstrates this problem. The sample application has a test case that verifies that the -Xbootclasspath parameter given in the <argLine> of the POM is properly passed to the JVM running the tests, but the test fails when using 2.4.x versions.
> If you modify the POM to use 2.3 version instead of 2.4.2, the tests pass.
--
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-461) -Xbootclasspath specified in
not passed to forked JVM
Posted by "Jason Voegele (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130018#action_130018 ]
Jason Voegele commented on SUREFIRE-461:
----------------------------------------
Can you confirm that this issue exists? I've included a sample project that demonstrates the issue.
> -Xbootclasspath specified in <argLine> not passed to forked JVM
> ---------------------------------------------------------------
>
> Key: SUREFIRE-461
> URL: http://jira.codehaus.org/browse/SUREFIRE-461
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4, 2.4.1, 2.4.2
> Reporter: Jason Voegele
> Attachments: surefire-argline-bug.tar.gz
>
>
> The 2.4.x versions of maven-surefire-plugin do not propagate the bootclasspath to the forked JVM that executes the tests.
> I have attached a sample project that demonstrates this problem. The sample application has a test case that verifies that the -Xbootclasspath parameter given in the <argLine> of the POM is properly passed to the JVM running the tests, but the test fails when using 2.4.x versions.
> If you modify the POM to use 2.3 version instead of 2.4.2, the tests pass.
--
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