Re: RE: RE: [equinox-dev] OSGI Bundles: alternate manifest.mf location

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

Not really.  The JDT classpath,
depending on how you look at it, contains either a) the source location
(e.g., p1/src), b) the output location (e.g., p1/bin) or the list of "other
things" (e.g., p2, foo.jar, ...).  None of these are suitable
homes for the manifest.  

Jeff

"Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

07/06/2006 11:16 AM

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

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

On 7/6/06, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
wrote:

Yes PDE performs some magic on the bundle classpath when selfhosting. It
gives to OSGi a map of bundleId to paths to add to the bundle-classpath
(the manifest is not modified on disk). 
However modifying the location of the manifest represents a chicken &
egg problem, since in order to provide the aforementionned map PDE needs
to read the id of the bundle which it gets from the manifest file. Therefore
the first level of support required to do this would be to let PDE knows
on a project basis where each manifest file is. 


Could PDE just get the manifest from the classpath, and the classpath from
the JDT project configuration ?

Tom
 
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev