Ah, very right. Now I see your commits from last week. I am surprised that Felix 2 is apparently broken now. I can try looking at that, time permitting, but that's pretty low on my list.
I believe the OSGi jruby classloader will handle embedded jars just fine, but if there's a particular class or gem you'd like tested, I could add that. The current test simply ensures we can: 1) Load OSGiScriptingContainer 2) Can java_import a class not shipped with JRuby (as long as a bundle that can see it was given as a parameter to the scripting container). 3) Can actually call a method on that imported class. Also, the profiles on the original jruby-osgi-test allowed running the tests under either equinox, felix4 or felix2. On Sep 17, 2013 9:37 AM, "christian" <m.krist...@web.de> wrote: > great that there is someone with osgi knowhow looking at that ;) > > but I have the feeling you missed the current state of osgi: > > $ mvn -Pcomplete > > will run the osgi IT which is now in maven/jruby-complete/src/it/osgi-test > which is just copy and paste of the old code with some adjustments to get > it pass. whether passing that test means a lot I do not know. > > the bouncy-castle jars are bundled within the META-INF/jruby.home along > with a number of other jars - not sure what the issue there is but any gem > with jars will have the same issue - the jruby-classloader loading a > vendored jar. > > > so it would be great to use the integration test from jruby-complete as a > starting point. > > - christian > > >
