Community
Participate
Working Groups
Created attachment 98856 [details] patch Created from bug 228517. - start Eclipse - install feature via old UM UI - restart - uninstall feature via old UM UI Note that feature is re-installed. This is how the old update manager uninstalls features: - it removes the feature from the list of features in the site in the platform.xml - (for a USER-EXCLUDE policy) it adds all the file paths for all of the feature's bundles to the site policy's plug-in list - it drops a file (configuration/org.eclipse.update/toBeUninstalled) which contains a list of all the feature names that will be uninstalled along with their corresponding site url from the platform.xml - on startup, the plug-ins are ignored because of their include in the plug-in list in the site policy - the update.scheduler bundle adds an extension to the UI's earlyStartup extension point which goes and looks for the toBeUninstalled file - the file is parsed and it is determined what needs to be removed from the file-system and deletion is done - platform.xml is updated (the files are no longer needed in the site policy's plug-in list) I have attached a patch which handles the filtering out of the features that are contained in the toBeUninstalled file. (the bundles are already filtered out via the site policy filter list).
+1 on this patch. There is a remaining issue with uninstalling a feature installed into a different site, but this patch enables the basic uninstall case and moves us in the right direction.
Created bug 230508 to address open issue about uninstalling from an extension location. Closing.
