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

Bug 345927

Summary: 'Plug-in from Existing JAR Archives' of exported JAR gives invalid .project file
Product: [Eclipse Project] PDE Reporter: Ben Cox <ben.cox>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: alexander.fedorov, ben.cox, Vikas.Chandra
Version: 3.6.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug investigate

Description Ben Cox CLA 2011-05-16 08:23:50 EDT 
Build Identifier: M20110210-1200

When using the 'Plug-in from Existing JAR Archives' wizard on a JAR which was created by using the default 'JAR file' export on a Java project, the resulting .project file doesn't have an org.eclipse.pde.PluginNature, org.eclipse.pde.SchemaBuilder or org.eclipse.pde.ManifestBuilder.

It would appear that the .project file is simply copied from the JAR file, without adding any PDE behaviour, which breaks us when we try to find all plug-in projects.

Reproducible: Always

Steps to Reproduce:
1. Create a plain (non-plugin) Java Project.
2. Export using 'Export' -> 'JAR File' -> 'Finish' (which by default includes .project file).
3. Import using 'New' -> 'Plug-in from Existing JAR Archives' -> 'Add External' -> select exported JAR file -> Add name -> 'Finish'.
4. Open new .project file
5. 'org.eclipse.pde.PluginNature', 'org.eclipse.pde.SchemaBuilder' and 'org.eclipse.pde.ManifestBuilder' missing.
Comment 1 Eclipse Genie CLA 2019-04-30 17:37:29 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2021-04-22 02:17:50 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-04-13 11:12:58 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.