Community
Participate
Working Groups
I have a case where the planner discovers 4 conflicting dependencies (sample report below). When examining the individual explanations that are provided by the PlannerStatus.getExplanations() method, I can only find explanations for the branches leading up to the first two conflicts. There's no mention of the latter two. This is problematic in the b3 aggregator since we aim to provide information about exactly which contributions it is that are problematic. Is this per design? Does p2 stop generating details once it has found two conflicting entries? Cannot complete the install because of a conflicting dependency. Only one of the following can be installed at once: Scala Plugin 2.0.0.beta08-28-201107121559-7d78460 (org.scala-ide.sdt.core 2.0.0.beta08-28-201107121559-7d78460) Scala Plugin 2.0.0.beta08-29-201107121555-7d78460 (org.scala-ide.sdt.core 2.0.0.beta08-29-201107121555-7d78460) Scala Plugin 2.0.0.nightly-29-201107190021-ad5bb29 (org.scala-ide.sdt.core 2.0.0.nightly-29-201107190021-ad5bb29) Scala Plugin 1.1.0.201105291637-milestones-M01 (org.scala-ide.sdt.core 1.1.0.201105291637-milestones-M01)
In this case I think the message is misleading because the explanation message is created from all the elements that are singletons in the slice, however not all of them may be in conflict.
So what you're saying is that we should have more trust in the explanations than in the original message?
Thomas, p2 provides only one explanation at the time, because this is the simplest way to proceed. If you need multiple explanations (e.g. all possible ones), that is possible but not trivial, but will need to be implemented in Sat4j first :) http://jira.ow2.org/browse/SAT-2
Does this bug need to be restricted to committers only?
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.
