It should be imported not exported. Typically you get a NoClassDefFoundError when something error'd out in the class mentioned... in this cause you need to see the cause of the exception further down in the stack.... maybe your activator isn't in the jar since the package isn't mentioned in the private section. If a package isn't mentioned in one of the manifest headers, I don't think it get's included in the jar.... can you confirm it it there?
Ryan On Apr 10, 2014 9:29 AM, "vickyk" <[email protected]> wrote: > vickyk wrote > > When I deploy the artifact I get this > > Caused by: java.lang.NoClassDefFoundError: > > org/osgi/framework/BundleActivator > > Any idea why this happens? It should be available to the osgi bundle > without > an explicit export of the org.osgi.framework package. > > > > > -- > 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-tp4032661p4032681.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
