[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_77010 ] Kenney Westerhof commented on MSUREFIRE-121: --------------------------------------------
The main question here is why do you need to add classes to the boot classpath? It uses an -X option, which is JRE specific; it's better not to fiddle with the boot classpath. I'm sure there's a perfectly legal usecase (java.lang.instrument stuff maybe?), but what is it? > 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 > Issue Type: Bug > Affects Versions: 2.2 > Environment: xp > Reporter: Dan Tran > Fix For: 2.3 > > 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
