Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 251017

Summary: [ui] Check for updates... should not be available in the menu if all IU's are locked
Product: [Eclipse Project] Equinox Reporter: Susan McCourt <susan>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: Ed.Merks, pascal
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Susan McCourt CLA 2008-10-15 18:15:12 EDT 
The check for updates handler should probably have some enablement logic.  Updates won't be allowed, for example, if the user is running a read-only shared install and hasn't installed anything else.

If all of the IU's present are locked for updates, then the handler should probably be disabled.

In the installed software view, this is depicted by graying out the update button when a locked IU is selected, or if all are locked.  But in the "Check for Updates..." workflow, there's no hint currently that everything is locked.
Comment 1 Susan McCourt CLA 2008-10-15 18:17:34 EDT 
Marking 3.5 for now.  Note that this still doesn't quite help the user who doesn't realize they are running a shared install.  Another possiblity would be to rework the code path for "check for updates" so that we can explain more specifically that the user can't update because the product is locked.  See also bug #232107
Comment 2 Susan McCourt CLA 2008-10-15 18:40:26 EDT 
See also bug #241683
Comment 3 Susan McCourt CLA 2009-07-09 17:09:07 EDT 
bulk update:  UI bugs not yet assigned a milestone are returned to the inbox.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:03:45 EDT 
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.
Comment 5 Ed Merks CLA 2020-02-20 05:56:51 EST 
The current state hasn't seem to bother anyone in the last 10 years.