Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321044 - Enable 1.7 compiler compliance in JavaSE-1.7.profile
Summary: Enable 1.7 compiler compliance in JavaSE-1.7.profile
Status: CLOSED DUPLICATE of bug 344833
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7.1   Edit
Assignee: Thomas Watson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 321035
  Show dependency tree
 
Reported: 2010-07-27 11:59 EDT by Markus Keller CLA
Modified: 2011-08-04 14:26 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2010-07-27 11:59:25 EDT
In HEAD, we can revert bug 309163 again and enable 1.7 compiler compliance in the JavaSE-1.7 profile.

Fix is to revert attachment 165464 [details] from bug 309163 comment 17.

Corresponding UI bug is bug 321035.
Comment 1 Thomas Watson CLA 2010-08-13 09:44:19 EDT
I will release this to HEAD.
Comment 2 Thomas Watson CLA 2010-08-13 09:46:38 EDT
Fixed.
Comment 3 John Arthorne CLA 2011-04-08 13:31:15 EDT
Since we have decided that Java 7 will not be supported by JDT in 3.7, it seems this change was premature and should be reverted again. Currently this lets you create a project that claims to have 1.7 class file compatibility, which is incorrect.
Comment 4 John Arthorne CLA 2011-04-08 13:36:54 EDT
Reopening to consider reverting for 3.7.
Comment 5 Thomas Watson CLA 2011-04-08 13:57:36 EDT
Moving this but out to 3.8 to enable 1.7 compiler settings again.  Opened bug342322 to address changing back to 1.6 settings in 3.7.
Comment 6 Thomas Watson CLA 2011-06-08 11:31:00 EDT
Move all 3.8 bugs to Juno.
Comment 7 Dani Megert CLA 2011-06-08 11:37:22 EDT
Sorry, but we will need this in 3.7.1.
Comment 8 Thomas Watson CLA 2011-08-04 14:26:43 EDT

*** This bug has been marked as a duplicate of bug 344833 ***