Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320933 - Confusing BREE quick fix proposal
Summary: Confusing BREE quick fix proposal
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.7 M1   Edit
Assignee: Curtis Windatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 12:48 EDT by Michael Rennie CLA
Modified: 2010-08-04 12:01 EDT (History)
1 user (show)

See Also:

Attachments
screen shot of the quickfix + settings (138.06 KB, image/png)
2010-07-26 12:48 EDT, Michael Rennie CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2010-07-26 12:48:31 EDT 
Created attachment 175241 [details]
screen shot of the quickfix + settings

build: I20100720-0800

I had created a new plugin project and noticed that there was a warning on my MANIFEST.MF. The warning was for no EE defined, so I activated the quick-fix which proposed I set the BREE to 1.6. The problem is that the EE defined in the Java settings for the project is J2SE-1.2, which is my case is bound to JDK 1.4 (on the installed JREs / EE pref page).

I would have assumed that the quick fix would try to match the BREE to any EE setting already on the project.
Comment 1 Curtis Windatt CLA 2010-07-28 12:31:44 EDT 
Fixed in HEAD.  See BundleErrorReporter.java.  The current logic didn't consider the classpath entry at all.  I changed the logic to check the classpath entry to see if it specifies an EE.  If it specifies a JRE, we look for a exact match EE to that JRE.  Failing those steps, we fall back on using the default JRE's matching EE.
Comment 2 Curtis Windatt CLA 2010-08-04 12:01:14 EDT 
Verified in I20100804-0100