Community
Participate
Working Groups
Allow uninstalling features. The update manager can disable features and plug- ins, but this is done without deleting their files. The update manager should keep track of the features and plug-ins that it installs, and fully support uninstalling them. [Platform Update] [Theme: Rich client platform]
There is already some code that logs the install (which plugins are instlled). I do not believe we log up to the file. There is a *2 phase commit* system where plugin.xml and feature.xml are *installed* when the whole feature is installed Uninstall is present but disable, but needs to be improved as we may uninstall a feature in a shared site.
*** Bug 36662 has been marked as a duplicate of this bug. ***
The external sites added via the links mechanism can be tagged as "read-only", which means they are not updatable (no installs or uninstalls can happen in those sites). Configuration states has been moved outside the workspace, so theoretically one should be able to install/uninstall features at will, provided that installers have configured the links accordingly (updateable or non- updateable). Also, inside the .config directory there is a file named "registry" that keeps track of which plugins and features have been installed by the update manager. Only those plugins and feature can be uninstalled. This is work in progress, so if you have any concerns/suggestions please add your comments here.
Uninstall support was released in the M3 build: - in order to uninstall a feature, the feature must first be unconfigured (disabled) - to see disabled features, turn off the filter in the configuration view (Help->Software Updates->Manage Configuration and toggle the third icon on the toolbar) - after disabling a feature, you may choose not to restart the workbench, then uninstall the feature, and then press OK to restart - only features (and their plugins) installed by the update manager can be uninstalled. In the M3 build, the uninstall action is enabled for all the disabled features, but nothing get removed from the disk. The latest build should fix this, so the uninstall action is disabled on natively installed features. - as mentioned before, if you want to use linked extensions to other eclipse sites (such as other eclipse installations), then you should define the link as "read-only" by prepending "r " in the path. Here is what the link file would look like: path=r d:/other/eclipse/product Use uninstalling carefully, as the features and plugins are completely removed from the file system, so you cannot revert to previous configurations that depend on the uninstalled features/plugins.
