Bug 27705 - [resources] Use of preferences in Core should be more explicit
Summary: [resources] Use of preferences in Core should be more explicit
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 RC2   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2002-12-04 17:00 EST by Rafael Chaves CLA
Modified: 2004-06-10 13:55 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 Rafael Chaves CLA 2002-12-04 17:00:44 EST
Workspace preferences, usually exposed only through 
org.eclipse.core.resources.IWorkspace#getDescription/setDescription, are now 
(2.1 M4) also available through the workspace plugin preferences. It does not 
matter which mechanism users use to set them (see bug 21977). The preferences' 
names were made publicly available through constants in 
org.eclipse.core.resources.ResourcesPlugin class. Users can now watch changes 
in the configurations through the property change mechanism provided by 
org.eclipse.core.runtime.Preferences. 

We must make reflect these changes in the API, namely:

- IWorkspace#setDescription changes the preferences store, saving it, and may 
fire property change events - and the situations where CoreExceptions may occur 
should be made more vague (e.g. if an error occurs while setting the 
description) - since now we don't get any exceptions while saving the 
preferences store;
- IWorkspace#getDescription gets its values from the preferences store;
- preferences' names declared as constants in ResourcesPlugin should refer the 
reader to IWorkpaceDescription correspondent getters.
Comment 1 DJ Houghton CLA 2004-06-10 13:55:40 EDT
Fixed and released to HEAD.