Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 139284 - Annotation Processing dialog has problems with Apply button
Summary: Annotation Processing dialog has problems with Apply button
Status: RESOLVED DUPLICATE of bug 137398
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 3.1.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Walter Harley CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 137398
Blocks:
  Show dependency tree
 
Reported: 2006-04-28 15:24 EDT by Adrian Grealish CLA
Modified: 2006-05-01 19:50 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Grealish CLA 2006-04-28 15:24:53 EDT
When you turn project specific settings off on the Annotation processing Dialog then hit apply then re-enable project spcific settings the dialog is in odd state where the rest of the dialog is still disabled for user edit.

Repro
---------
1. Create Java project
2. Go to project properties --> Java Compiler --> Annotation Processing
3. Enable project spcific settings
4. Enable annotation processing
5. Hit OK
6. Go back to project properties --> Java Compiler --> Annotation Processing
7. Disable project specific settings
8. Click apply
9  Re-enable project specific settings, now unable to to use any other component on dialog because they are not active
Comment 1 Walter Harley CLA 2006-05-01 19:50:54 EDT
Essentially the same as bug 137398, or bug 111144.  This is yet another instance of the problem where WorkingCopyManager has cached a copy of a node, and that node then gets deleted (because disabling project preferences removes the per-project settings node).

The reason the controls are disabled is that the initialization code has failed.  In the error log, note the following (partial) stack:

java.lang.IllegalStateException: Preference node "org.eclipse.jdt.apt.core" has been removed.
at org.eclipse.core.internal.preferences.EclipsePreferences.checkRemoved(EclipsePreferences.java:145)
at org.eclipse.core.internal.preferences.EclipsePreferences.internalGet(EclipsePreferences.java:512)
at org.eclipse.core.internal.preferences.EclipsePreferences.get(EclipsePreferences.java:363)
at org.eclipse.ui.internal.preferences.WorkingCopyPreferences.put(WorkingCopyPreferences.java:149)
at org.eclipse.jdt.apt.ui.internal.preferences.BaseConfigurationBlock$Key.setStoredValue(BaseConfigurationBlock.java:151)
at org.eclipse.jdt.apt.ui.internal.preferences.BaseConfigurationBlock.useProjectSpecificSettings(BaseConfigurationBlock.java:915)
at org.eclipse.jdt.apt.ui.internal.preferences.BasePreferencePage.enableProjectSpecificSettings(BasePreferencePage.java:54)
at org.eclipse.jdt.internal.ui.preferences.PropertyAndPreferencePage$1.dialogFieldChanged(PropertyAndPreferencePage.java:108)
at org.eclipse.jdt.internal.ui.wizards.dialogfields.DialogField.dialogFieldChanged(DialogField.java:70)


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