Generate OSGi MANIFEST.MF headers in the build
Issue #26
wontfix
From https://java.net/jira/browse/JAUDIOTAGGER-440
When JAT is build into a JAR, it would be good if the MANIFEST.MF generated inside the JAR could include OSGi headers. This makes JAT an OSGi 'bundle' and suitable for deployment into an OSGi container.
This gives a number of benefits:
Easy deployment for existing users of OSGi containers
Capability to modularise code better an disallow access to certain packages
Able to run multiple versions of JAT at once and have versions updated without restarting the VM
I ported bliss to the OSGi platform and as part of this I adapted JAT to be an OSGi bundle. My method and example MANIFEST.MF is documented here:
http://www.elstensoftware.com/blog/2012/08/15/osgi-jaudiotagger/
BTW, adding these headers to the MANIFEST doesn't affect 'vanilla' Java VMs using the same JAR.
Comments (3)
-
reporter -
reporter - changed status to wontfix
Wont fix
-
LOL, you're keeping up with the blog I see! Fair decision.
- Log in to comment
Seeing as bliss is abandoning OSGI installs because if various issues I think its fair to close this