Man, I really wish I had more time to work on all this, but I can at least
provide a bit more of an info dump on the current state, and what I'm
working on to improve it for the future.
So, I mentioned that the require 'openssl' test is failing. It's failing
with felix, because we currently assum
not sure but
$ mvn clean install -Pcomplete
from the main directory should work (and works for me).
-christian
On Sun, Sep 22, 2013 at 7:43 PM, Anthony Juckel wrote:
> First, to answer our question, we don't need any OSGi metadata in any jars
> embedded in jruby-complete in order for it to be
First, to answer our question, we don't need any OSGi metadata in any jars
embedded in jruby-complete in order for it to be a well-behaved bundle.
Even so, my require 'openssl' test is failing under OSGi, and I think it's
because a bundle:// URI is getting passed through to RubyInstanceConfig,
but
hi
is there a chance to get the modular jruby artifacts running on osgi - do
all the dependent jar be osgi for that ? I am rather new to osgi ;) so
excuse my ignorance !
On Tue, Sep 17, 2013 at 4:49 PM, Anthony Juckel wrote:
> Ah, very right. Now I see your commits from last week. I am surpris
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 o
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 p
