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

Bug 260953

Summary: Importing fragment without Import/Export-headers forgets java nature
Product: [Eclipse Project] PDE Reporter: Benjamin Muskalla <b.muskalla>
Component: UIAssignee: Curtis Windatt <curtis.windatt.public>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: caniszczyk, contact, curtis.windatt.public
Version: 3.5   
Target Milestone: 3.5 M7   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
target none

Description Benjamin Muskalla CLA 2009-01-13 19:03:40 EST 
N20090109-2000

Importing a fragment from the target platform which does not specify any import/export headers ends up as pde project without java nature.
See PluginImportOperation#needsJavaNature.

I don't think that this is the right way as you can have correct fragment project without the corresponding manifest headers.
Comment 1 Benjamin Muskalla CLA 2009-01-13 19:04:55 EST 
Created attachment 122481 [details]
target

mini-target platform to test the behavior
Adding "Export-Package: p" to the manifest of the fragment leads to the correct behavior.
Comment 2 Curtis Windatt CLA 2009-01-16 15:01:45 EST 
Don't have the time to look at this right this minute, but as it affects import I will look at it in 3.5 sometime.
Comment 3 Curtis Windatt CLA 2009-03-20 15:01:00 EDT 
The way we are determining java requirements doesn't make much sense.  We skipped over your fragment because it doesn't import/export, and we do add the java nature to doc bundles because they require org.eclipse.help.  I changed the code to check for a BREE, which all plug-ins containing java code require as well as for exported bundles.