Community
Participate
Working Groups
The remoteSystemsViewPreferencesActions seems to be obsolete. It should be possible to achieve the same via org.eclipse.ui.viewActions or org.eclipse.ui.commands All the client needs to do, is contribute a handler class that opens a specific preference page. This handler class can be derived from a utility class in RSE. Because the specific preference page is likely contributed as well, so the preference page's plugin needs to be activated anyways, it is very likely that having to specify a class doesn't even activate an extra plugin. Migration docs should be written explaining how a custom preference page can be contributed. As an Example, the existing RSE preference page show action should be contributed through one of the two methods mentioned above. When this is done, * class SystemCascadingPreferencesAction will most probably be obsolete (since core Eclipse cares for populating the menu already), class * class SystemShowPreferencesPageAction will need to become API since clients will need to derive from it - unless we'd be able to use the commands extension point with command parameters to modify operation of the action, then it can remain internal.
Extension point removed, checkin comment: [185552][api] Remove remoteSystemsViewPreferencesActions extension point For 2.0RC1, and org.eclipse.ui.handlers extension should be created to allow extenders contribute Preference Page Open shortcuts again. This request is being tracked by bug #186769.
[target cleanup] 2.0 M7 was the original target milestone for this bug
