[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66194 ]
Trygve Laugstol commented on MSUREFIRE-121: ------------------------------------------- I would still like to understand the real use case that you have here. Will classes in the bootstrap classloader really load stuff from the system classpath (i.e. the one given with -classpath)? Instead of adding all of the dependencies to the -classpath it might be better to be able to give a set of artifacts to add. Ideally it should be given a set of artifacts and use Maven's code to resolve the rest of the required artifacts. > 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
