Apply for 1.1.3. Pretty innocuous.

Great!

Applied in r7188.

Houston, we have a problem.

After applying the OSGI changes, it appears our spec runs have started to fail. "rake spec:ji" runs a small portion of the main build and then executes JRuby against a bunch of java integraiton specs. However with the OSGI changes, we get a class not found exception looking for MainExitException.

The primary thing I noticed is that the bnd runs every time we do a build, and many (most?) of those times we already have an existing JAR we're updating. Is it possible that repeat bnd against an updated jar could be causing some kind of problems?

I know nothing about bnd and we've got 1.1.3 supposed to go out in a day or two, so unfortunately I'm going to have to revert this. If you can come up with a modification and explanation that allows ant test and rake spec:ji to execute correctly, we can probably get it back in.

Even worse, under soylatte (JDK6 port for OS X) the OSGI changes appear to cause segfaults somewhere in libzip. Double ouch. Might be good to contact us on IM or IRC as soon as possible, or this isn't going to make 1.1.3.

Bump until we can solve the two issues cited above.

The patch seems to use Bnd to wrap the jar generated by Ant.

There are other alternatives:
1. Use Bnd itself to generate the JAR
2. Use Bnd to generate the MANIFEST.MF first, then use Ant jar task to include that Bnd-generated manifest

The "safest" way for now is option #2, which I think is enough for most purposes... although it's not "clean" i.e. it's not the Bnd intended way of life.

After tests pass again etc. option #1 can be used.

Option #3 is the best actually: Use Maven build system and maven-bundle-plugin

I'll try to help solve this bug.

Thanks in advance for your help Hendy. Hopefully we can get this back in for JRuby 1.1.4 in the next couple weeks.

Thanks Charles.

This is a(nother) patch to JRuby trunk to OSGi-fy it.

This patch is very similar to previous patch, I simply reorders it and tweak the manifest a bit.

Apart from the patch, it also needs http://www.aqute.biz/repo/biz/aQute/bnd/0.0.249/bnd-0.0.249.jar downloaded into "build_lib"

In my system all JRuby tests still pass (ant test) and I also made sure that it actually works inside OSGi by creating a test project here:

https://scm.ops4j.org/repos/ops4j/laboratory/users/ceefour/jruby-test/

(login as anonymous)

To use my jruby-test, after checking out the project run "mvn install pax:provision"
(you need to have Maven installed)

This is an updated patch which also exports org.jruby.internal

Previously I didn't export this, but I also want to modify the jruby engine at JSR223, and the JRuby JSR223 engine uses org.jruby.internal package so I have to export it too. Besides it might be useful for other people.

We have a new patch and people want this.

Parallel work at JSR223: https://scripting.dev.java.net/issues/show_bug.cgi?id=37

Another test is available to demonstrate jruby and jsr223-jruby in OSGi working properly.

The JSR223 for JRuby is already updated in JSR223 CVS (see https://scripting.dev.java.net/issues/show_bug.cgi?id=37 ), however we'll need to wait JSR223 team to release the updated JARs.

Test project available at (SVN):

https://scm.ops4j.org/repos/ops4j/laboratory/users/ceefour/jruby-jsr223-test

To test:

mvn install pax:provision

The required dependencies (jsr223-jruby, jruby) must be available in your local Maven repo.

Fixed in commit 7437. I applied the latest patch and it seems to work after being bundled via 'ant dist'. I also updated our poms to reflect bnd as a build dependency. I did not test this, but as I have some other heinious maven work before 1.1.4 release I will deal with any mistakes then.