Bug 237044

Summary: [quick fix] Quickfix toggles JRE1.6 instead of 1.5 as advertized
Product: [Eclipse Project] JDT Reporter: Philipe Mulet <philippe_mulet>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: martinae
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Screenshot of EE configuration for 1.5 none

Description Philipe Mulet CLA 2008-06-13 06:54:54 EDT
Build id: I20080609-1311

After using a quickfix for updating compiler+JRE settings to 1.5, the JRE is 1.6 !?

Assuming you have installed JREs for: 1.4.2, 1.5.0 and 1.6.0 (1.6 being default)

Steps
1. create a new Java project
2. specify use of 1.4.2 JRE and compliance
3. create a new class:
   public class X<E> {
   }
4. apply quickfix for error on <E> parameter suggesting changing compliance 
   to 1.5
5. observe that JRE is actually switched to 1.6 instead of 1.5
Comment 1 Philipe Mulet CLA 2008-06-13 06:58:40 EDT
Created attachment 104838 [details]
Screenshot of EE configuration for 1.5
Comment 2 Philipe Mulet CLA 2008-06-13 06:59:22 EDT
To clarify: only JRE got mishandled, compiler compliance is properly set to 1.5
Comment 3 Eclipse Genie CLA 2020-05-31 12:12:39 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 4 Eclipse Genie CLA 2022-05-22 15:07:03 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.