You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2006/05/29 03:46:41 UTC
[jira] Updated: (MSUREFIRE-121) ability to add dependency to jvm's
classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=all ]
Dan Tran updated MSUREFIRE-121:
-------------------------------
Attachment: MSUREFIRE-121-booter.patch
MSUREFIRE-121.plugin.patch
> 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