Bug 14062 - JDK Compliance against a project
Summary: JDK Compliance against a project
Status: RESOLVED DUPLICATE of bug 7091
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.1 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-17 20:00 EDT by Brent Crammond CLA
Modified: 2002-09-23 04:36 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 Brent Crammond CLA 2002-04-17 20:00:51 EDT 
It would make sense to be able to set the JDK Compliance level against a 
project.  This would allow for compiling different projects under different 
level of compiler. The main reason for being able to this is that you may want 
to compile say a applet project with 1.1 compliance, but be developing new 
projects with 1.4 compliance.

Currently JRE is definable at the project level and to make this useful would 
also require the JDK compliance at the project level.
Comment 1 Philipe Mulet CLA 2002-04-18 03:58:37 EDT 
Currently all settings are global indeed. Per project settings are not 
currently on the 2.0 plan.
Comment 2 Philipe Mulet CLA 2002-04-18 07:20:23 EDT 
Will reconsider post 2.0
Comment 3 Philipe Mulet CLA 2002-07-25 06:59:41 EDT 
Reopening
Comment 4 Philipe Mulet CLA 2002-07-25 07:00:58 EDT 
Clearing resolution
Comment 5 Philipe Mulet CLA 2002-08-09 09:50:52 EDT 
Variable values per project are along the same line as option values per 
project.

*** This bug has been marked as a duplicate of 7091 ***
Comment 6 Philipe Mulet CLA 2002-09-23 04:36:25 EDT 
Solved in latest, IJavaProject can be specified custom options, in particular 
compliance can be toggled on a project basis (once UI surfaces it).