I need help debugging what should be a straightforward OSGi classloading
problem, running Groovy in OSGi.
The stuff is here:
mvn install pax:provision will run the application. mvn pax:eclipse will
also be working to generate Eclipse projects.
The offending line is so simple:
new GroovyShell().evaluate("println 'Hello World from Groovy!';");
Which should just run the groovy script, but it can't.
Please help me diagnose this problem, you may commit directly to that lab if
you wish (it's OPS4J anyway).
I think it will involve a change in Groovy's manifests, please inform. I
want to get this fixed so upcoming Groovy (1.5.7 and 1.6 release) can
flawlessly be used inside OSGi.
Note that I use Groovy snapshot because that's the only version that has
proper resolvable OSGi manifests out-of-the-box (see:
A side note is that Groovy 1.5.1 artifact available from SpringSource
Enterprise Bundle Repository can work just fine when used as a replacement
dependency. I'm hoping that someone can "backport" i.e. contribute that
positive change back to Groovy itself, so there'd be no need to wrap it just
to make it work with OSGi.
I can only presume there aren't many Groovy devs that care about OSGi so
hopefully we can help push this forward.