Bug 79883

Summary: [prefs] -pluginCustomization doesn't pick up compiler preferences
Product: [Eclipse Project] JDT Reporter: Nikolay Metchev <nikolaymetchev>
Component: CoreAssignee: Frederic Fusier <frederic_fusier>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: dj.houghton
Version: 3.1   
Target Milestone: 3.1 M5   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Nikolay Metchev CLA 2004-12-01 11:12:05 EST 
Eclipse 3.1M3

I am using the -pluginCustomization eclipse startup parameter. In my ini file I
have the line:

org.eclipse.jdt.core/org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=warning

I also have the line
org.eclipse.jdt.ui/org.eclipse.jdt.ui.formatterprofiles= (rest ommited)

If I startup on a clean workspace the I have all my various formatter profiles
correct however the unusedPrivateMember is set to Ignore.
Comment 1 Frederic Fusier CLA 2004-12-24 06:25:54 EST 
Fixed.

Now JavaCore default preferences are initialized using extension and preferences
initializer as it should be for new eclipse preferences mechanism.

Doing this, customized options are added after JavaCore plugin have set its
default => everything works fine now.

[jdt-core-internal]
No specific test case added as JUnit tests does not really allow to add
customized plugin options.
Comment 2 Frederic Fusier CLA 2005-01-03 13:09:53 EST 
Reopen as fix a bad side effects (JavaProject specific compiler settings are not
read...).
Fix has been removed from HEAD.
Comment 3 Frederic Fusier CLA 2005-01-04 05:59:15 EST 
Finally put back into HEAD as the issue came from patching process.
While installing new jdtcore.jar, we also need to remove
configuration/org.eclipse.core.runtime directory which seems to store
information about plugin.xml files...
Comment 4 David Audel CLA 2005-02-14 11:34:41 EST 
Verified for 3.1M5