Bug 60325 - [RCP] review AbstractUIPlugin.initializeDefaultPluginPreferences() API
Summary: [RCP] review AbstractUIPlugin.initializeDefaultPluginPreferences() API
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P2 major (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2004-04-28 16:32 EDT by Jim des Rivieres CLA
Modified: 2004-05-07 14:36 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jim des Rivieres CLA 2004-04-28 16:32:27 EDT 
Plugin.initializeDefaultPluginPreferences() is now deprecated, and there is a 
new story in place.

AbstractUIPlugin re-implements this method, and offers it as API to its 
subclasses. Review the AbstractUIPlugin API to see what should be done here.
Comment 1 Nick Edgar CLA 2004-04-28 22:09:00 EDT 
Since this method will still be used if the app is using
org.eclipse.core.runtime.compatibility, and if the plugin doesn't provide its
own preference initializer, then it seems like all we should do here is copy
down the deprecated tag and info from Plugin.
Comment 2 Nick Edgar CLA 2004-05-07 14:36:33 EDT 
I've added:

     * 
     * @deprecated this is only called if the runtime compatibility layer is
     *             present. See the deprecated comment in
     *             {@link Plugin#initializeDefaultPluginPreferences}.

and a similar comment in the legacy^2 method initializeDefaultPreferences
(IPreferenceStore).