Bug 70986

Summary:	[Prefs] Old Java project prefs are not all stored while migrating to new API
Product:	[Eclipse Project] JDT	Reporter:	Frederic Fusier <frederic_fusier>
Component:	Core	Assignee:	Frederic Fusier <frederic_fusier>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.0
Target Milestone:	3.1 M2
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Frederic Fusier

2004-07-28 10:58:47 EDT

While starting a 3.0 workspace with I200407271028 build, I see that new
.settings folder appears in projects I have set specific compiler options.
This is normal as using 3.1, we have migrated projects compiler options from
self-hand made to new Platform/Core Preferences API...

However, looking at one .prefs file contents, I see that only modified options
are stored in this file. This is not correct as all compiler preferences, even
those values are the same than workspace ones, should be present in this file.

Comment 1 Frederic Fusier

2004-07-28 11:01:24 EDT

While migrating preferences, we do not write preference which have a default
value in Javaproject.updatePreferences(IEclipsePreferences)...
This test must be removed.

Comment 2 Frederic Fusier

2004-07-28 12:24:13 EDT

Fixed and released in HEAD.

All compiler options for a project are now stored in IEclipsePreferences while
migrating a 3.0 or earlier workspace.

[jdt-core-internal]
Change done in JavaProject.updatePreferences(IEclipsePreferences) method.
I've tested this change (ie. open a 3.0 workspace with I200407271028 + this
fix), but no test case was added as it's not really possible to simulate this
migration using JUnit...

Comment 3 Frederic Fusier

2004-09-14 07:15:15 EDT

*** Bug 68988 has been marked as a duplicate of this bug. ***

Comment 4 David Audel

2004-09-23 12:36:01 EDT

Verified in I200409230100.