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:
BTW, adding these headers to the MANIFEST doesn't affect 'vanilla' Java VMs using the same JAR.