[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RE: RE: [equinox-dev] OSGI Bundles: alternate manifest.mf location
- From: "Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>
- Date: Thu, 6 Jul 2006 17:16:13 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=UX1Rkf0sTWfcCl90aJYkmsh8IECCYWLBUz55ooOQwTFSjX15tuj3pWgXm3RBvQxGOKcQAsr9CBKAeC+WDlDyZtpRe9EuBxALaUZbUgvrad+RyWy6v4aI0HB6pv+CKaOBq+ZrOXd4/PikQQBHhy6iAanJKAGNxx85YfytdMPJemg=
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
Could PDE just get the manifest from the classpath, and the classpath from the JDT project configuration ?