Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359732

Summary: Allow user to specify alternative location of MANIFEST.MF in a PDE project
Product: [Eclipse Project] PDE Reporter: Matthew Adams <matthew>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: curtis.windatt.public, pwebster, remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Matthew Adams CLA 2011-10-03 12:04:50 EDT 
Build Identifier: I20110613-1736

PDE projects currently require a META-INF/MANIFEST.MF file, relative to the project root directory.  If your project is also intended to be used in an OSGi environment, you usually use maven-bundle-plugin to generate proper OSGi manifests.  Problem is, maven-bundle-plugin uses the file META-INF/MANIFEST.MF that the user has to include via hand-editing whether you want it to or not (see https://issues.apache.org/jira/browse/FELIX-3142).

If the eclipse user could set a PDE project property that specified the location of the MANIFEST.MF file used for PDE purposes, then the one generated by maven could be used.  In that way, if a maven builder (from m2e) is included in the project and its maven-bundle-plugin were bound to the process-classes phase and used its "manifest" goal, then the PDE builder, set by the user to execute after the maven builder, would see the generated manifest at target/classes/META-INF/MANIFEST.MF (or wherever maven-bundle-plugin wrote the file).


Reproducible: Always

Steps to Reproduce:
(enhancement request)
Comment 1 Curtis Windatt CLA 2011-10-03 12:24:47 EDT 
PDE supports a flexible bundle root location (bug 297895).  However, the files must still be in the expected bundle structure (build.properties and plugin.xml at the root, manifest.mf in the META-INF folder).  Furthermore, there is currently no way to set this from the UI (bug 153023).

Moving to UI as this does not involve API Tools.

If this could be satisfied by (bug 153023), please mark it as a duplicate.  There are no plans to work on it for 3.8 due to lack of resources, but we do try to be responsive to community contributions *hint* *hint*.
Comment 2 Curtis Windatt CLA 2013-01-04 10:56:10 EST 

*** This bug has been marked as a duplicate of bug 153023 ***