Community
Participate
Working Groups
I had an Eclipse SDK installed and had updated it into 3.7.2 release candidates. Today, when I wanted to update that install to RC3, updating failed due to conflicts caused by components like "Add-on Function for p2", "Equinox p2 Provisioning for IDEs." and similar. It seemed I had run into the same situation again as discussed in http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06447.html an its answers. Bottom-line: once you check any of the components of your initial profile for explicit update, that component will be locked and no further update is possible - until you "uninstall" the component (which basically is a NOP at this point - hopefully). First, to me it is unintuitive that checking something for update (not installing anything new) will block subsequent updates. This includes my puzzlement that p2 cannot see, that the dependency blocking the update is going to be removed by the same update: after the update no installed component will be requesting the "conflicting" version. Second, if p2 really must behave this way, I would really suggest helping the user to clean up. For this particular problem I could think of an operation: "remove all redundant/explicit dependencies".
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
