Bug 135348 - Changing compiler compliance level should disable errors/warnings not available in selected language version
Summary: Changing compiler compliance level should disable errors/warnings not availab...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-06 14:38 EDT by Max Gilead CLA
Modified: 2006-04-06 14:38 EDT (History)
0 users

See Also:

Attachments
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 Max Gilead CLA 2006-04-06 14:38:39 EDT 
Changing compiler compliance level should disable errors/warnings not available in selected language version.

For example my default compiler compliance level is 5.0 and I have most of 5.0-specific warnings/errors enabled. There are however several project I'm working on that require 1.4-level compliance. I change compiler level for them but also need to reconfigure warnings because Eclipse complains about eg. missing @Override annotations in 1.4 project.

I believe setting compiler compliance level to 1.4 should disable all 5.0 checks in selected project, similarly for older releases. Of course it only applies to projects which use global compiler warnings configuration.