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

Bug 50921

Summary: [plan item] Add support for new plug-in format
Product: [Eclipse Project] PDE Reporter: Jim des Rivieres <jeem>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P4 CC: eclipse, ed.burnette
Version: 2.1Keywords: plan
Target Milestone: 3.0 M9   
Hardware: All   
OS: All   
Whiteboard:

Description Jim des Rivieres CLA 2004-01-29 17:27:33 EST 
Add support for new plug-in format. PDE should provide support for developing 
and deploying plug-ins with explicit OSGI bundle manifests. The goal is 
provide a seamless experience for developers working with a mix of traditional 
and new style plug-ins.
Comment 1 Wassim Melhem CLA 2004-03-24 13:11:15 EST 
Progress made on this front in M8:
1. You can import plug-ins that contain manifest.mf.
2. Plug-ins with manifest.mf are recognized as plug-ins in the PDE model 
registry.
3. PDE can compute classpaths correctly for plug-ins with manifest.mf by using 
the Core state/resolver support.
4. You can launch a runtime workbench and these plug-ins will be correctly 
picked up.
5. You have the option to create a plug-in with manifest.mf

Item left for M9:
1. Build/export plug-ins with manifest.mf
2. PDE must not choke on a plugin.xml file that contains only extensions and 
extension points.  
3. PDE manifest builder must not flag a plugin.xml file that does not contain 
plugin id, name, etc. as error if the plug-in contains a manifest.mf
Comment 2 Wassim Melhem CLA 2004-05-19 00:23:20 EDT 
This item is completely finished.
Plugins flying solo on a manifest.mf are treated as regular plugins in all 
aspects of self-hosting.
Importing, exporting, classpath computation, running a runtime workbench.
Also the same manifest editor is used to edit plugin.xml and manifest.mf.