How can Eclipse plugin-setup take effect over all workspaces...?

Thread view:

stigva@gmail.com - 17 Mar 2006 14:01 GMT

Hello,

It appears that plugin setup usually follows the workspace. That
becomes a problem when plugins are required to assume global
configuration (fx. Eclipse proxy-setting) for all workspaces - and we
might want to delete earlier workspaces.

Destination for plugin setup can _not_ be controlled with the Eclipse
configurator startup option "-configuration" because this only
redirects stuff in the <eclipse_installation_dir>/eclipse/configuration
directory. The Eclipse startup option "-data" just repositions contents
of the workspace - but source code/plugin-setup changes still end up
the same place.

Is there an option to seperate the persisted plugin setup from a single
workspace? Am I really the only person, which would like to see plugin
setup take global effect over all workspaces ?

regards

Stig

Reply to this Message

Daniel Rohe - 18 Mar 2006 20:39 GMT

stigva@gmail.com schrieb:

> Hello,
>
[quoted text clipped - 17 lines]
>
> Stig

Preferences in Eclipse 3.1 are scoped. This means you have different
scopes where to store your preferences. The default scope used in
plug-in is instance scope. Preferences in this scope are stored in the
metadata directory in your instance location. Another scope is the
configuration scope. Preferences in this scope are stored in the
configuration directory of your Eclipse installation. With the Resources
Plugin you have another scope, the project scope. Preferences in this
scope are stored on a per project base.

To retrieve the preference store instantiate a scope and call
getNode(<plugin_id>) with your plugin-id to retrieve an instance of
IEclipsePreferences which provides the interface to the preference system.

Kind regards,
Daniel

Reply to this Message

How can Eclipse plugin-setup take effect over all workspaces...?

Free Magazines