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

Bug 321035

Summary: Enable 1.7 compiler compliance in the UI
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: UIAssignee: Markus Keller <markus.kell.r>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, darin.eclipse, deepakazad, markus.kell.r, Olivier_Thomann, srikanth_sankaran
Version: 3.7   
Target Milestone: 3.8 M6   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 321043, 321044    
Bug Blocks:    
Attachments:
Description Flags
Fix none

Description Markus Keller CLA 2010-07-27 11:25:59 EDT
Enable 1.7 compiler compliance in the UI (revert bug 309163).
Comment 1 Markus Keller CLA 2010-07-27 11:34:52 EDT
Workaround in 3.6 builds is to set the following options in
.settings/org.eclipse.jdt.core.prefs
to 1.7 manually:

org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.7
org.eclipse.jdt.core.compiler.compliance=1.7
org.eclipse.jdt.core.compiler.source=1.7
Comment 2 Markus Keller CLA 2010-07-27 11:47:47 EDT
Created attachment 175330 [details]
Fix
Comment 3 Olivier Thomann CLA 2010-07-27 11:55:05 EDT
The copyright in ComplianceConfigurationBlock should point to 2010, shouldn't it ?
Comment 4 Markus Keller CLA 2010-07-27 12:03:39 EDT
> The copyright in ComplianceConfigurationBlock should point to 2010, shouldn't
> it ?

Yep, fixed that and committed to HEAD. You will see wrong version warnings and a wrong default compliance for JavaSE-1.7 EE/VMs until bug 321043 and
bug 321044 are fixed as well.
Comment 5 Dani Megert CLA 2011-04-11 03:03:44 EDT
We need to remove this for 3.7 and then set target to 3.8.
Comment 6 Dani Megert CLA 2011-04-15 10:05:07 EDT
(In reply to comment #5)
> We need to remove this for 3.7 and then set target to 3.8.

Done. See patch in bug 342391.

To enable again simply set
org.eclipse.jdt.internal.corext.util.JavaModelUtil.HIDE_VERSION_1_7 to 'false';
Comment 8 Markus Keller CLA 2012-03-20 06:49:01 EDT
*** Bug 344729 has been marked as a duplicate of this bug. ***