You could also remove the manifest bundle headers and run it through bnd
to see what it would have generated. Is this a Maven project? If so,
you could use packaging of bundle.
google search: osgi bnd
On 04/10/2014 07:47 AM, Ryan Moquin wrote:
Have you tried viewing the bundle headers or info from the Karaf
console? I could be wrong, but the astricks seem in odd positions in
your manifest. Did you generate the manifest yourself?
Off the top of my head, for karaf 3.0.0, I would do a bundle:list to
find the bundle number, then do bundle:headers # and bundle:info #
(where # is the id of the bundle) and see if it highlights anything in
read, which it does if there is something that it doesn't like in your
manifest. Is the bundle in a started state?
Ryan
On Apr 10, 2014 2:21 AM, "vickyk" <[email protected]
<mailto:[email protected]>> wrote:
Some more information,
I modified the manifest thinking version and main class entry would be
messing up but that also seem not to work, here is new manifest entry
Manifest-Version: 1.0
Export-Package: *org.dallaybatta.osgi.api;version="1.0.0"*
Built-By: vickykak
Build-Jdk: 1.7.0
Bundle-Version: 1.0.0
Bundle-Name: Core API
Bundle-Activator: org.dallaybatta.osgi.Activator
Created-By: Apache Maven
Bundle-SymbolicName: api-bundle-V1
Import-Package:
org.osgi.framework,*org.dallaybatta.osgi.api;version="1.0.0"*
Archiver-Version: Plexus Archiver
I though change the version in the import package will load
specific class
which does not be the case when I run the simple example.
--
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-tp4032661p4032671.html
Sent from the Karaf - User mailing list archive at Nabble.com.
