No prob... just some advice, if you get to the point where you think you have no choice but to create a manifest yourself (such as turning a 3rd party jar into a bundle) because there are some osgi unfriendly classloading tricks or something else going on (and you are sure that you won't need to modify the manifest anymore), then I would still use the maven bundle plugin to generate the manifest.mf, then remove the plugin and copy the manifest.mf into your src/main/resources..... I think there are ways to still handle those advanced scenarios using the plugin, but just in the off chance you hit a situation where you feel that's the only way, then it's best to start from the generated one and then make whatever small customization you need to.
Glad you got it working. Ryan On Thu, Apr 10, 2014 at 10:45 AM, vickyk <[email protected]> wrote: > rkmoquin wrote > > I see you are generating the entries manually with the jar plugin, don't > > do > > that.. use the maven-bundle-plugin... you are missing the osgi imports > and > > if you use the maven bundle plugin it will automatically generate your > > imports section for you. Also, don't use the felix dependency in your > > pom, > > use the osgi core and osgi compendium dependencies in your bundle... that > > way you aren't relying on any specific implementation unless you have to. > > You are spot on and I suspected this could be causing the issue. > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Unable-to-do-load-BundleActivator-after-package-is-exported-in-manifest-for-a-bundle-tp4032661p4032687.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
