Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
JustinEd3Accepted solution
Adobe Employee
October 16, 2015

Hi,

Just to be clear, every JAR file has a MANIFEST.MF file in it. OSGi defines additional headers which go in the manifest, but the core file and format (and placement within the JAR file) is defined by the Java core specification.

Regards,

Justin

View in thread

2 replies

Adobe Employee
JustinEd3Adobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

Just to be clear, every JAR file has a MANIFEST.MF file in it. OSGi defines additional headers which go in the manifest, but the core file and format (and placement within the JAR file) is defined by the Java core specification.

Regards,

Justin

Translate
Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

OSGi jar which are known as bundle requires OSGi metadata in its manifest so that an OSGi framework can manage the visibility of classes between bundles. A JAR without this metadata would only contain invisible classes, could not see any classes from other bundles, nor could it get started in any way. The Import-Package manifest header tells what packages should be made visible to the bundle, and the Export-Package defines the packages in the bundle that should be made visible to others.

Normal jar wouldnt have this metadata or a manifest file

Translate
Terms & ConditionsAccessibility statement

Loading footer...