Hi,
the maven-bundle-plugin's job is to package the bundle and create the
bundle manifest. So if all packages/classes you expect are included in
the bundle jar and the manifest content matches what you configured in
the plugin configuration the plugin has done it's job.
If you have a specific osgi related question about the correct manifest
content for your use-case or the behaviour of an osgi implementation you
might have more luck to get this answered on a more osgi related
mailinglist (like that of the implementation you are using).
-Tim
Arash Amiri schrieb:
Hi,
um...
sometimes (I say "sometimes" because I really dont know what the cause
is), a bundle, that I create with the maven-bundle-plugin, misses, once
deployed, its own packages.
e.g. I have a package "org.myapp.meta" in my maven project.
I configure the maven bundle plugin (in the same project) the following
way:
...
<Import-Package>org.myapp.*;resolution:=optional</Import-Package>
<Export-Package>org.myapp.*</Export-Package>
...
when I deploy it in equinox, it gives me an error such as:
Missing imported package org.myapp.meta
I dont get this, since the jar file contains the package.
Yet, I have to admit that the bundle has other dependencies which are
not (yet) satifsfied.
e.g. the org.myapp.meta package uses "org.openrdf.elmo" which is in a
bundle not yet deployed (since I have to create it first).
my question:
Is it a maven bundle plugin configuration issue or is it simply Equinox
that refuses to import packages which have unresolved references?
greetings,
arash
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
