Community
Participate
Working Groups
Open Manage Configuration (Help > SoftwareUpdates > ManageConfiguration). Expand the tree to see a list of Eclipse features. Select a few of them by clicking while holding the Ctrl key down. The right panel shows the actions you can perform (like Disable or Show properties). Select one of those actions and you will see it only applies to the first feature in the selection. Either the operations offered should apply to all selected items, or multiple selection should not be allowed. Personally I'd prefer if multiple selection was enabled, and the action is performed against all. For example, if I have a number of patches applied, I'd like to be able to select a group of them and disable or enable in one convenient action. Another odd behaviour related to this: Select one enabled feature (like Eclipse Platform) and you'll see the following operations allowed: Scan for Updates Disable Show properties Now select a second feature (like PDE) and the list remains the same. Now select a third feature (like Equinox) and for some reason "Show properties" gets removed from the choices. It seems like there is some logic attempting to limit choices based on multi-select but it's just not working well.
This is one of the most annoying things after updating many plugins (especially because of bug 174821). Maybe uninstalling multiple (disabled) features at once should be a task of its own?
There are also open defects on disabling/uninstalling mutually dependent features at once. The code is not treating this as one atomic operation and therefore will not work (because disabling feature by feature leaves the state in error, but disabling all at once does not).
I improved the behaviour of multiple selection so that only operations that apply to multi-selection are showing. However, I didn't fix batch uninstall because it can only work for independent features. Patches will work actually if they are not mutually dependent. However, removing a set of features that prereq each other will not work because jobs are validated and executed one by one. All jobs should be validated in a batch and then executed without further validation. Well, not in 3.3 unless somebody has time to do it for me and not introduce new APIs :-).
Lowering the severity. This is a real bug, but there is a workaround.
The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2.
