Bug 255276 - [ui] The UI could avoid showing patches that are not applicable
Summary: [ui] The UI could avoid showing patches that are not applicable
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.5   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: polish
Depends on:
Blocks:
 
Reported: 2008-11-13 15:52 EST by Pascal Rapicault CLA
Modified: 2020-02-20 05:51 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2008-11-13 15:52:54 EST 
The wizard could hide patches for which the IIUPatch#getLifeCycle is not met in the installed profile. Still I would provide an option in case somebody wanted to install the patch along with the feature to be patched.
Comment 1 Susan McCourt CLA 2008-11-13 17:28:37 EST 
Marking M5 to consider possible affordances for patches that match the lifecycle.  In bug 216032 we consider showing better affordances on available items that indicate when something is already installed, when something is an upgrade, etc.

So the question is do we filter out these patches or just have an affordance that makes it more clear that a particular patch is relevant?
Comment 2 Susan McCourt CLA 2009-07-09 17:09:14 EDT 
bulk update:  UI bugs not yet assigned a milestone are returned to the inbox.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:58 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 4 Ed Merks CLA 2020-02-20 05:51:33 EST 
This seems a corner case for which there has never been time and will never be time. :-(