On Thursday 22 August 2013 12:37 PM, Dawid Loubser wrote:
Ah, I didn't even know that BND Tools (used from ant) put in a -
non-standard and meaningless, as you say - "Private-Package" manifest
entry in the JAR. I can see how that would confuse the original poster
coming from there, then.
Impedance mismatch or not, we are running a very large (many bundles)
supplier integration system on OSGi, built and tested with maven, using
strong design-by-contract and test-driven-development practices. The
amount of code and complexity in relation to development team size is
staggering, and I wouldn't dream of doing it without Maven!
Now that you know missing Private-Package in manifest.mf is not going to
change how your OSGi bundle behaves, you should be able to continue to
use maven and bundle plugin. Private-Package is one of the inputs to
bundle-plugin's bundle goal to control what your bundle will be made up
of. You may like to take a deeper look at how bundle plugin makes a jar
file. It's not same as how jar or zip tool works.
I don't want to confuse you, but there is another option wherein you use
bundle plugin's manifest goal to generate OSGi manifest only. Then the
manifest becomes part of the jar or war that maven builds. Many
developers find it easier this way, because the content of the jar is
not driven by OSGi metadata; it's the vice-versa.
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
