Re: [osgi-dev] Bundle starts although no OSGi headers in its Manifest

2018-02-12 Thread Neil Bartlett via osgi-dev
Your manifest does not contain the declaration "Bundle-ManifestVersion: 2". That means it is interpreted as "Bundle-ManifestVersion: 1"... in other words an OSGi Release 3 (or older) compatible bundle. Before Release 4, OSGi had no mandatory manifest headers, even Bundle-SymbolicName. Therefore

[osgi-dev] Bundle starts although no OSGi headers in its Manifest

2018-02-12 Thread Eran Twili via osgi-dev
Hi, We are implementing OSGi in our product (embedding Equinox programmatically). Designing our Bundles installation error handling, we run some tests. Surprisingly, we see that when we install a regular jar archive in the FW, it's getting installed, resolved and even active, without any