[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=all ]
Kenney Westerhof closed MSUREFIRE-121.
--------------------------------------
Assignee: Kenney Westerhof
Resolution: Fixed
Fixed in revision 488508. Added useSystemClassloader parameter that puts ALL
test classpath elements
in the system classloader. This is the only safe way to do it.
> ability to add dependency to jvm's classpath rather in surefirebooter
> classloader
> ---------------------------------------------------------------------------------
>
> Key: MSUREFIRE-121
> URL: http://jira.codehaus.org/browse/MSUREFIRE-121
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: xp
> Reporter: Dan Tran
> Assigned To: Kenney Westerhof
> Fix For: 2.3
>
> Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch,
> MSUREFIRE-121.plugin.patch2, MSUREFIRE-121.plugin.patch3
>
>
> I have a usecase where i have a jar file got loaded by -Xbootclasspath, that
> jar file then loads classes from another jar ( my dependency)
> expected in the classpath.
> The problem is that surefire plugin does not add my dependencies at JVM
> commanline thru -classpath option, but after the JVM starts
--
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
