[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66146 ]
Trygve Laugstol commented on MSUREFIRE-121: ------------------------------------------- I still don't understand what you're after here, you're saying something about the boot class path and something about the -classpath. How will making a URLClassLoader containing all the JAR files different from adding them to -classpath? The ability to add stuff to the boot strap class path is useful, but you need to explain why you need to add stuff to -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
