[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66070
]
Dan Tran commented on MSUREFIRE-121:
------------------------------------
I am after placing the project dedendencies on the -classpath list of the fork
command
My surefire plugin would look like this
<dependendcies>
<!-- need this on JVM -classpath list -->
</dependencies>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<forkMode>once</forkMode>
<workingDirectory>${project.build.directory}</workingDirectory>
<argLine>-Xrunpri:${basedir}/src/test/resources/optimizeit.xml
-Xbootclasspath/p:myboot.jar</argLine>
<allowClasspathElementsOnCommandline>true</allowClasspathElementsOnCommandline>
</configuration>
</plugin>
myboot.jar after booting up needs to reference some other class in my project
dependencies expected on -classpath
> 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
