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

Just curious, I am all for flexibility, but your argument seems to be
that Eclipse is not flexible when it comes to PDE and PDE build looking
for potential alternate locations for the manfest. And you are asking
for a way to add that flexibility in Eclipse.
The argument could be turned around:
Why would Maven be so inflexible as to mandate the manifest to be in a
resource directory?
And force a certain project layout based on its build system?


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 Ravindar Reddy
> Sent: Wednesday, July 05, 2006 10:46 PM
> To: Equinox development mailing list
> Subject: Re: RE: [equinox-dev] OSGI Bundles: alternate 
> manifest.mf location
> Just to add to what Alex said below - I understand that the 
> OSGI package needs the META-INF in the jar at top level. All 
> I am asking is that the source location in OSGI plugin 
> project could be anywhere (like 
> resources/META-INF/MANIFEST.MF) that gets relocated to 
> META-INF/MANIFEST.MF for final bundle package. 
> The reason I am doing this is to use "Apache Maven" for 
> headless builds and use Eclipse as IDE for OSGI bundles. 
> Currently I am using normal java project for OSGI bundles as 
> I can not relocate the META-INF and let build.properties know 
> about it. Seems like all you need is to introduce an extra 
> property to inform the PDE as to where META-INF is located. 
> Just with this functionality I would be able to build OSGI 
> bundles in both (Maven abd Eclipse) with the same source layout
> - Ravi R