Add support for managed boot classpath aditional jars
-----------------------------------------------------

                 Key: PAXRUNNER-176
                 URL: http://issues.ops4j.org/jira/browse/PAXRUNNER-176
             Project: Pax Runner
          Issue Type: New Feature
            Reporter: Alin Dreghiciu
            Assignee: Alin Dreghiciu
            Priority: Minor


As from OPS4J mailing list:

For some reasons (e.g some classes use systemClassLoader), there may be a case 
that some jars need to be pulled out of the bundle and added in bootclasspath.

For instance,

 --vmOptions=-Xbootclasspath/p:./lib/korkor.jar;./lib/didi.jar

I don't like the fact I need to manually copy these two jar files and then put 
them in the lib folder. Assuming both of these jars are mavenized project,  I 
would like to know does the pax-runner capable to handle this situation in more 
dynamic way?

Suggestion:

Pax-runner somehow understands the "mvn" file protocol, so I can do this

 
--vmOptions=-Xbootclasspath/p:mvn:org.ops4j/korkor/0.1-SNAPSHOT;mvn:org.ops4j/didi/0-1-SNAPSHOT.jar


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to