Thank you for the comment.Â
I hope next version of OSGi implementations will add support for this classpath case.Â
There's no real need to do this. You have to generate the bundle/manifest from something; that should have full visibility of the JARs that are contained within the bundle at build time, so it's a trivial build issue to solve.
If you want to use something which installs all bundles in a directory, then either Peter's FileInstall (available at felix.apache.org
) or the P2 Director is able to bulk-install all JARs in a directory into a running OSGi runtime. There's no concept of an 'ext dir' per se, given that all bundles must be installed ahead of time, but the tools mentioned above allow you to trivially add a new bundle into a runtime by copying into a new area. In the case of your example, you'd do:
java -Dfelix.fileinstall.dir=c:\jars -jar org.eclipse.osgi_*.jar
osgi> install fileinstall.jar
osgi> start 1
Note that whilst P2 is the Eclipse case, there's next to no documentation on how to use it, and so the Felix FileInstall is generally preferred for that reason.
PS The mailing list is for development of equinox; there's a newsgroup for user questions like this next time.