Bug 68988 - [1.5] All project compiler new preferences should be stored when reading old 3.0 ones
Summary: [1.5] All project compiler new preferences should be stored when reading old ...
Status: RESOLVED DUPLICATE of bug 70986
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-30 07:35 EDT by Frederic Fusier CLA
Modified: 2004-09-14 07:15 EDT (History)
1 user (show)

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 Frederic Fusier CLA 2004-06-30 07:35:27 EDT 
Using 3.0 + Cheetah06.

I launch Cheetah06 on a 3.0 workspace in which some projects have specific
compiler preferences.
I see that a new file has been created: .settings/org.eclipse.jdt.core.prefs.
This is quite normal as this is the place where project "new" preferences are
stored now...

However, if I edit this file, I noticed that only modified compiler options are
there. This is not correct, all compiler options should be present in this file,
even if they have default value. This was done to prevent compilation result to
change on this project if user changed workspace compiler options...
Comment 1 Philipe Mulet CLA 2004-06-30 07:54:15 EDT 
We should store all project specific settings (not only these different from 
defaults), but UI should allow one to only customize a subset of the 
preferences. For lots of them, defaults are just fine, and I may want these to 
be the same as my workspace ones (user decision); in which case, I would only 
want to ensure a few settings are customized.
Comment 2 Frederic Fusier CLA 2004-09-14 07:15:14 EDT 

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