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

Bug 409853

Summary: [remediation][ui] Provide an option to pass operation provisioning context
Product: [Eclipse Project] Equinox Reporter: Pascal Rapicault <pascal.rapicault>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 4.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Pascal Rapicault CLA 2013-06-04 10:06:09 EDT 
When a provisioning wizard constructs the remediation operation, no provisioning context is set. This means that all the p2 repos will be consulted thus guaranteeing that the most suitable solution is found.

However there are some situations where contacting all the repos could be a problem (e.g. spotty connection) and it would help if the set of repos contacted would be the one that was set in the original operation (thus respecting the "contact all update sites" option in the install software dialog)..

Given that this issue is transversal to all wizards (install, update, etc.), we should introduce a configuration scope preference that let the user decide what he wants to see happening in the remediation.

It worth nothing though that the solutions returned by remediation will be different whether all the repos are contacted or not. For example if I'm trying installing JBoss tools and it is blocked by tool XYZ (for example because of low level dependencies) then remediation with contacting all the repos may find a solution where XYZ is updated, whereas when only the initial repos are used it is most likely that the appropriate solution is to uninstall XYZ.
Comment 1 Pascal Rapicault CLA 2014-05-05 10:20:45 EDT 
Will not be addressed in Luna.
Comment 2 Eclipse Genie CLA 2019-06-24 16:12:55 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.

--
The automated Eclipse Genie.