Community
Participate
Working Groups
20021113 - add new task tags to the workspace compiler settings - remove them all for one of the projects - rebuild happens - reopen the project's properties, look at settings - all task tags are still there
A JCore problem: IJavaProject.setOptions() uses setPreferences which looks at a value to set, compares it with the default value. If it's the same it stores 'null'. However, 'null' means, take it from the workspace settings, but that's not what I meant. The workspace settings could change, and I still want the project setting to have the specific setting.
This is the standard story for preferences. No preference means use defaults. Maybe this should be better documented.
For the project specific settings null has a different meaning: Use the _workspace_ settings. Note that I want to express: Use project specific setting 'xx'.
We should probably introduce an extra possible value: "Workspace Default" to identify this scenario.
I think the current design is fine, just change the implementation to an own preference store that does not clear a setting if it is equal to it's default.
Fixed.
Verified.
