Closed paulvi closed 8 years ago
@paulvi I don't think this is related to osgi-run
in the sense there's nothing I can do to help make this work. osgi-run
's only purpose is to create an OSGi runtime with the bundles you have and run it easily... if the bundle is not being created correctly, you need to see what's going on with the bundle creator, in this case the gradle-bundle-plugin, I guess.
Why does the bundle need osgi.wiring.package=commonj.work
? Where this comes from? If it were a Gradle dependency of your project, osgi-run
would have added it to the runtime... maybe you just need to add a osgiRuntime 'org:commonj.work:version'
declaration in the Gradle deps?
Please see my answer on Stackoverflow. Closing this as this is not applicable to this plugin.
in quartz-sample-nested-jars example:
https://github.com/paulvi/osgi-run/tree/master/osgi-run-test/quartz-sample-nested-jars
there's error, so resulted bundle is not ACTIVE in felix, and can't be started.
full log
ref #32 , https://github.com/TomDmitriev/gradle-bundle-plugin/issues/54 @TomDmitriev @rotty3000
My TODO is raise on stackoverflow.com