Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350197

Summary:	Generator settings not all removed when disabling project settings
Product:	z_Archived	Reporter:	Justin Spadea <jspadea>
Component:	EDT	Assignee:	Justin Spadea <jspadea>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	alicec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Justin Spadea

2011-06-23 17:23:42 EDT

Have an EGL project use project-specific settings. Set some generators on it. Then choose a file or package in the project, and give it different generators.

Now uncheck the project-specific settings box in the property page, so that workspace defaults get used. There's still some project-specific settings in the .settings folder.

For example in org.eclipse.edt.ide.core.prefs:
generatorIds//eglsource/a/b/c=org.eclipse.edt.ide.gen.JavaGenProvider

This was where I had package a.b.c overriding the generator settings.

And in org.eclipse.edt.ide.compiler.prefs:
javaGenDirectory//eglsource/a/b/c=P/generatedJava

The generator-specific setting was also not cleaned up for this resource.

The project-level settings were correctly removed.

Comment 1 Alice Connors

2011-07-05 10:29:34 EDT

At the folder and file level, we don't necessarily need to allow you to go back to workspace settings.  Consider only allowing project-level settings (check and disable the 'Enable project-level settings' box) for properties at these levels.

Comment 2 Justin Spadea

2011-07-08 11:06:51 EDT

Part of multi-bug fix, files affected may include:

GenerationSettingsComposite
CompilerAndGeneratorControls
CompilerPropertyAndPreferencePage
PropertyAndPreferencePage
ProjectSettingsUtility
plugin.xml from edt.ide.ui

Comment 3 Justin Spadea

2011-09-15 11:30:30 EDT

Verified