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 Fabulich (JIRA)" <ji...@codehaus.org> on 2007/11/24 03:03:57 UTC
[jira] Closed: (SUREFIRE-117) ability to add dependency to jvm's
classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/SUREFIRE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-117.
---------------------------------
Resolution: Fixed
I'm confused by all the chatter on this bug. I just applied the patch from SUREFIRE-180 / SUREFIRE-118 which I THINK fixes this bug also (or, if that won't do it, you should be able to accomplish what you need to accomplish using the argLine parameter).
If not, please provide a reduced test case in the form of a minimal Maven project that highlights the problem.
> ability to add dependency to jvm's classpath rather in surefirebooter classloader
> ---------------------------------------------------------------------------------
>
> Key: SUREFIRE-117
> URL: http://jira.codehaus.org/browse/SUREFIRE-117
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Environment: xp
> Reporter: Dan Tran
> Assignee: Kenney Westerhof
> Fix For: 2.4
>
> 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