[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] OSGI Bundles: alternate manifest.mf location
- From: Ravindar Reddy <rroopreddy@xxxxxxxxx>
- Date: Wed, 5 Jul 2006 10:37:14 -0700 (PDT)
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=h/fYBa36CcJQX5is7+cQUBl/COdNbBcbrAftwRElvEVY1A5rQiY3t5ATzHR5ZeC7MbWWGCKt8Iso0kq3IfVF5N0pCmfFPUrRo4XMqKUPGT+PLWSq9pG7/kNfjaer6k9R0zVBbpXncoUnndwSyCOi7vOTCuzaYX6d1vKkw+lD9MM= ;
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 resources/META-INF/MANIFEST.MF from META-INF/MANIFEST.MF. Updated "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