[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] OSGI Bundles: alternate manifest.mf location

The OSGI spec is a little over-zealous in specing that all bundles are JARs.  I don't dispute what it says (though I don't recall it being that strong) but in practice several open source implementations that I know support installation of directory based bundles.  This gives you a clue as to why PDE is keen on the file being where it is and called what it is.  this approach allows you to turn around and simply run the project as a bundle without doing any whacky copy transformations or passing extra manifest location information into the runtime.


"Philippe Ombredanne" <pombredanne@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

07/05/2006 04:43 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

"'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>
RE: [equinox-dev] OSGI Bundles:  alternate manifest.mf location

Note that a jarred bundle could not be a standard Jar anymore if the
META-INF was anywhere else.

And an OSGi jarred bundle is always a valid Jar file.
>From the OSGi R4 spec:
"2.3.2 Java JAR File Restrictions
OSGi bundles are always valid JAR files."
"3.2.1 Bundle Manifest Headers
A bundle can carry descriptive information about itself in the manifest
that is contained in its JAR file under the name of

So putting the manifest anywhere would break OSGi compatibility afaict.


philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by Design (tm) - http://www.nexb.com
http://EasyEclipse.org  -  irc://irc.freenode.net/easyeclipse

-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Wednesday, July 05, 2006 10:51 AM
To: Ravindar Reddy; Equinox development mailing list
Cc: Equinox development mailing list; equinox-dev-bounces@xxxxxxxxxxx
Subject: Re: [equinox-dev] OSGI Bundles: alternate manifest.mf location

Yes, PDE requires the manifest file to be located in the META-INF/
folder at the root of the project.


Ravindar Reddy <rroopreddy@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
07/05/2006 01:37 PM Please respond to
Ravindar Reddy <rroopreddy@xxxxxxxxx>; Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

ToEquinox development mailing list <equinox-dev@xxxxxxxxxxx>
Subject[equinox-dev] OSGI Bundles:  alternate manifest.mf location

PDE Plugin project requires a valid Manifest to be present under
/meta-inf of the current OSGi bundle project in the workspace, and the
PDE dependencies virtual classpath variable mounts the deps mentioned in
the Manifest. Is there a way to use alternate location for OSGI
MANIFEST.MF file (e.g: resources/META-INF/MANIFEST.MF)?

I created a sample OSGI project and moved to the file to
"build.properties" to reflect this new location. The PDE generated
errors and was unable to mount the plugin deps mentioned in manifest.mf.

Is META-INf location is hard-coded somehow?

Any help is appreciated, thanks
-Ravi R_______________________________________________
equinox-dev mailing list

equinox-dev mailing list