Hi,
It always help me to find generation problems looking the plugin
declaration using the *effective POM*.
If you use Eclipse IDE, you can use the one provided by m2e's POM editor.
It is useful because it will show you a merge of the local plugin
configuration plus values coming from the pluginManagement and also the
ones inherited from parent POMs.
perhaps there are some configuration error that you are not seeing.
regards,
Cristiano
On 07/07/2016 11:38, Andreas Sewe wrote:
Hi,
I am using the maven-bundle-plugin 3.0.1 to create an OSGi bundle. May
Maven project has a packaging of "bundle" and the m-bundle-p generates a
MANIFEST.MF for me.
Alas, unlike what's described in the documentation, my exported packages
are *not* imported.
From the documentation [1]:
Any exported packages are also imported by default, to ensure a
consistent class space.
and
Additionally, it generates imports for every export to ensure package
substitutability, which is very important when working with
collaborating services.
I am not using any <instructions> except for <Bundle-DocURL> (IMHO,
${project.url} is a much better DocURL than
${project.organization.url}), so <Export-Package> and <Import-Package>
are using their default values.
Can someone please point out the mistake I am making here?
Best wishes,
Andreas
[1]
<https://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html>
