Bugzilla – Full Text Bug Listing
| Summary: | Confusing BREE quick fix proposal | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | UI | Assignee: | Curtis Windatt <curtis.windatt.public> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | curtis.windatt.public | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.7 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
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. Verified in I20100804-0100 |
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.