[
http://jira.codehaus.org/browse/SUREFIRE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164285#action_164285
]
jmfj commented on SUREFIRE-435:
-------------------------------
Added comment to
[SUREFIRE-510~http://jira.codehaus.org/browse/SUREFIRE-510?focusedCommentId=164278&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_164278]
Seems like the issue is still on.
> Maven Surefire should set system property java.class.path or something like
> surefire.java.class.path
> ----------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-435
> URL: http://jira.codehaus.org/browse/SUREFIRE-435
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Martin Burger
>
> In some of my test cases I fork another JVM instance that must have the same
> classpath as the executed test. I use the system property java.class.path to
> get the classpath.
> In Eclipse it works as expected, the system property java.class.path holds
> all the dependencies. But if I use Maven to run the tests, that system
> property holds just
> '/Users/mburger/bin/maven2/boot/classworlds-1.1.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/.compatibility/14compatibility.jar'.
> AFAIK the system property java.class.path is read only, so Surefire cannot
> set it. But it would be very nice to have some fall back like
> surefire.java.class.path. In my test cases I could use that system property
> as fall back when java.class.path does not contain the expected JAR files.
--
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
