[eclipse-dev] Evolving Preferences Work [Plug-in developers please read]

[DJ Houghton <DJ_Houghton@xxxxxxxxxx>]

Here is an update on the preferences work.

Conversion
=======
If you contribute preference pages, you should not be converting them to
the new APIs yet. Continue to call Plugin.getPluginPreferences(). The
backwards compatibility layer will suit your needs.

If you have information which is currently not stored in preferences and
not displayed in the preference pages (e.g. list of repository providers),
then feel free to start using the new APIs.

Also, people with project preferences that they would like to share are
encouraged to look at the new APIs.


Scopes
======
We have decided not to implement a User scope for 3.0. The user scope was
intended to mean preferences stored on a "per user basis, across all
configurations and all workspaces". (there is still the option of adding it
at a later time) The class UserScope will be removed in the nightly builds
and for the next integration build.

The Configuration scope refers to preferences stored in the configuration
location. It will still exist in 3.0 and allow users to share preferences
across the same configuration. (e.g. single install, multiple workspaces)

See related bug report on a proposal for the configuration location.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=54919


Directory Structure
============
The directory structure will change to
"<scopeRoot>/.settings/<qualifier>.prefs"

For instance:
"/workspace/MyProject/.settings/org.eclipse.core.resources.prefs"

Clients will still have access to the "scope location". (e.g.
/workspace/MyProject/.settings)


Documentation
==========
Available at the following link (might be split across lines):

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/documents/user_settings/index.html


Comments and discussion encouraged on the platform-core-dev mailing list or
in the associated plan item bug report:
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=36965