Bug 75230 - Java Compiler preferences page becomes unavailable after switch to and from project settings
Summary: Java Compiler preferences page becomes unavailable after switch to and from p...
Status: RESOLVED DUPLICATE of bug 68993
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: 3.1 M2   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-28 20:42 EDT by Jeff Norris CLA
Modified: 2004-09-29 03:24 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 Jeff Norris CLA 2004-09-28 20:42:48 EDT 
First an important note - I have the Cheetah (1.5) plugin installed.  Cheetah
contributes to the preferences page in question, so it may be to blame.  I can
reliably reproduce this bug on both RedHat Linux 9 and Windows XP.

To reproduce this error, follow these steps:

1.  Right click on a java or plugin project and select "Properties".
2.  Select the "Java Compiler" preference page
3.  Click "Use project settings" and click OK.  
4.  Eclipse will inform you of the need to do a full project build.  Click "Yes".
5.  The properties dialog will close.  Right click on the project again and
select "Properties" and return to the "Java Compiler" page.
6.  Click "Use workspace settings" and click OK.
7.  Eclipse will inform you again of the need to do a full project build.  Click
"Yes".
8.  The properties dialog will close again. 
9.  Right click on the project A THIRD TIME (stay with me here!)  Eclipse will
open an error dialog with the title "Could Not Accept Changes" and the message
"The currently displayed page contains invalid values".  The Java Compiler page
will not be visible.  You'll also get the following stack trace:

java.lang.IllegalStateException: Preference node "org.eclipse.jdt.core" has been
removed.
        at
org.eclipse.core.internal.preferences.EclipsePreferences.checkRemoved(EclipsePreferences.java:142)
        at
org.eclipse.core.internal.preferences.EclipsePreferences.keys(EclipsePreferences.java:575)
        at
org.eclipse.jdt.internal.core.JavaProject.getOptions(JavaProject.java:1438)
        at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:151)
        at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:206)
        at
org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:76)
        at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:700)
        at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:739)
        at
org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1097)
        at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:88)
        at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:129)
        at
org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86)
        at
org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:96)
        at
org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:75)
        at
org.eclipse.jdt.internal.ui.text.JavaReconciler.process(JavaReconciler.java:315)
        at
org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:204)
Comment 1 Frederic Fusier CLA 2004-09-29 03:24:23 EDT 
Please install 3.1 M2 which fixes this problem.
Note that now Cheetah plugin is no longer available.
To get 1.5 features latest implementation, you have to get 3.1 milestone or
integration builds.


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