[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66192
]
Dan Tran commented on MSUREFIRE-121:
------------------------------------
Ok, let me try to rephase in details so see it makes sense.
In my fork mode sample configuration, myboot.jar must be loaded via
-Xbootclasspath/p:myboot.jar command line.
myboot.jar then references, at boot time, some other classes in my project
dependency and FAILS since my dependendencies
are not loaded yet. They are loaded only after the JVM is fully constructed (
see SureFireBooter's main method ).
The solution is to place my dependencies as part of java.exe 's -classpath
list which currently contain only the sure-fire's plugin dependencies
(ie surefire-api, surefire-booter, etc)
here is my jvm command line example
java.exe -Xrunpri:${basedir}/src/test/resources/optimizeit.xml
-Xbootclasspath/p:myboot.jar -classpath <mydependencies> ...
> 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
> Type: Bug
> Versions: 2.2
> Environment: xp
> Reporter: Dan Tran
> Fix For: 2.3
> Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch
>
>
> 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
