Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311279 - [planner][explanation] Make sure all paths to singletons are presented in the error message
Summary: [planner][explanation] Make sure all paths to singletons are presented in the...
Status: CLOSED DUPLICATE of bug 261928
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Daniel Le Berre CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-01 07:48 EDT by Aaron Digulla CLA
Modified: 2010-05-08 10:02 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Digulla CLA 2010-05-01 07:48:47 EDT
Build Identifier: 20100204-0846

When I try "Check for Updates", I get lots of URLs which fail (all starting with "file:/". Where do they come from?

The operation then fails with:

Cannot complete the install because of a conflicting dependency.
  Software being installed: Eclipse IDE for Java EE Developers 1.3.0.20100315-0831 (epp.package.jee 1.3.0.20100315-0831)
  Software being installed: Eclipse Platform SDK 3.6.0.I20100429-1549 (org.eclipse.platform.sdk 3.6.0.I20100429-1549)
  Only one of the following can be installed at once: 
    Equinox Launcher 1.1.0.v20100419 (org.eclipse.equinox.launcher 1.1.0.v20100419)
    Equinox Launcher 1.0.300.v20090720 (org.eclipse.equinox.launcher 1.0.300.v20090720)
  Cannot satisfy dependency:
    From: Eclipse IDE for Java EE Developers 1.3.0.20100315-0831 (epp.package.jee 1.3.0.20100315-0831)
    To: org.eclipse.epp.package.jee.feature.feature.group [1.3.0.20100315-0831]
  Cannot satisfy dependency:
    From: Java EE IDE Feature 1.3.0.20100315-0831 (org.eclipse.epp.package.jee.feature.feature.group 1.3.0.20100315-0831)
    To: org.eclipse.platform.feature.group [3.6.0.v20100121-9hF78GK1FufosnFu87UwXZfHJWXovR-z-9b]
  Cannot satisfy dependency:
    From: Eclipse Platform 3.6.0.v20100121-9hF78GK1FufosnFu87UwXZfHJWXovR-z-9b (org.eclipse.platform.feature.group 3.6.0.v20100121-9hF78GK1FufosnFu87UwXZfHJWXovR-z-9b)
    To: org.eclipse.rcp.feature.group [3.6.0.v20100201-9GAcFGCFq7Lo_y4ElaEbOXNc]
  Cannot satisfy dependency:
    From: Eclipse Platform SDK 3.6.0.I20100429-1549 (org.eclipse.platform.sdk 3.6.0.I20100429-1549)
    To: org.eclipse.rcp.configuration.feature.group [1.0.0.I20100429-1549]
  Cannot satisfy dependency:
    From: Eclipse Product Configuration 1.0.0.I20100429-1549 (org.eclipse.rcp.configuration.feature.group 1.0.0.I20100429-1549)
    To: org.eclipse.equinox.launcher [1.1.0.v20100419]
  Cannot satisfy dependency:
    From: Eclipse RCP 3.6.0.v20100201-9GAcFGCFq7Lo_y4ElaEbOXNc (org.eclipse.rcp.feature.group 3.6.0.v20100201-9GAcFGCFq7Lo_y4ElaEbOXNc)
    To: org.eclipse.equinox.launcher [1.1.0.v20100307]

When I try to upgrade "Eclipse Platform" using http://download.eclipse.org/eclipse/updates/3.6milestones/, I get this error:

Your original request has been modified.
  "Eclipse Platform" is already installed, so an update will be performed instead.
Cannot complete the install because of a conflicting dependency.
  Software being installed: Eclipse Platform 3.6.0.I20100429-1549 (org.eclipse.platform.ide 3.6.0.I20100429-1549)
  Software currently installed: Eclipse Platform SDK 3.6.0.I20100129-1300 (org.eclipse.platform.sdk 3.6.0.I20100129-1300)
  Only one of the following can be installed at once: 
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20091210-1301
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20091030-1201
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20100312-1448
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20100129-1300
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20090917-0100
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20100429-1549
    org.eclipse.rcp.configuration_root.gtk.linux.x86_64 1.0.0.I20090806-1400
  Cannot satisfy dependency:
    From: Eclipse Platform 3.6.0.I20100429-1549 (org.eclipse.platform.ide 3.6.0.I20100429-1549)
    To: org.eclipse.rcp.configuration.feature.group [1.0.0.I20100429-1549]
  Cannot satisfy dependency:
    From: Eclipse Platform SDK 3.6.0.I20100129-1300 (org.eclipse.platform.sdk 3.6.0.I20100129-1300)
    To: org.eclipse.rcp.configuration.feature.group [1.0.0.I20100129-1300]
  Cannot satisfy dependency:
    From: Eclipse Product Configuration 1.0.0.I20100129-1300 (org.eclipse.rcp.configuration.feature.group 1.0.0.I20100129-1300)
    To: org.eclipse.rcp.configuration_root.gtk.linux.x86_64 [1.0.0.I20100129-1300]
  Cannot satisfy dependency:
    From: Eclipse Product Configuration 1.0.0.I20100429-1549 (org.eclipse.rcp.configuration.feature.group 1.0.0.I20100429-1549)
    To: org.eclipse.rcp.configuration_root.gtk.linux.x86_64 [1.0.0.I20100429-1549]

No other preinstalled update site offers anything useful. When I open "EPP Packages Repository - http://download.eclipse.org/technology/epp/packages/helios", I get "Java EE IDE Feature" but the version is 1.3.0.20100315-0831.

How do I upgrade

Reproducible: Always

Steps to Reproduce:
1. Download M5 (eclipse-jee-helios-M5-linux-gtk-x86_64.tar.gz, MD5 b534c019ee5d66b4b07be6c74f748d38)
2. Add "Eclipse Platform SDK"
2. Run "Check for Updates"
Comment 1 Pascal Rapicault CLA 2010-05-01 16:29:12 EDT
You are experiencing this problem because what you have installed is JEE M5 (and probably the Eclipse Platform SDK M5) and at this point only the Platform SDK M7 is available. Therefore p2 is looking for an update it tries to install Platform M7 on top of JEE M5 and it does not work.
You should be available to update once the JEE package M7 (and its update site) will be made available later this week.

Marking this for 3.6 just to sure to verify.
Comment 2 Aaron Digulla CLA 2010-05-01 18:34:41 EDT
Your explanation makes sense. Here are two suggestions to make the error message easier to understand:

1. The message doesn't say where the dependency "Equinox Launcher 1.0.300.v20090720" comes from, so I can't see which plugin blocks the update.

2. Sometimes, the name of a plugin is used ("Equinox Launcher 1.1.0.v20100419") and sometimes the plugin ID ("org.eclipse.equinox.launcher [1.1.0.v20100307]")

Either supply always both or only the name (which should be unique, right?)
Comment 3 Pascal Rapicault CLA 2010-05-02 23:04:42 EDT
> 1. The message doesn't say where the dependency "Equinox Launcher
> 1.0.300.v20090720" comes from, so I can't see which plugin blocks the update.
  This is definitely something that we should be able to improve.

> 2. Sometimes, the name of a plugin is used ("Equinox Launcher 1.1.0.v20100419")
> and sometimes the plugin ID ("org.eclipse.equinox.launcher [1.1.0.v20100307]")
> 
> Either supply always both or only the name (which should be unique, right?)
  The user readable name is shown for the IUs (along their id) and for the requirements we show the id because there is no user readable string there. We used to only show the id everywhere but users could not relate from the ID to the element they had selected in the UI.

I've renamed this bug to focus on making sure we show all the paths from all roots to the singletons.
Comment 4 Daniel Le Berre CLA 2010-05-08 04:38:23 EDT
(In reply to comment #3)
> > 1. The message doesn't say where the dependency "Equinox Launcher
> > 1.0.300.v20090720" comes from, so I can't see which plugin blocks the update.
>   This is definitely something that we should be able to improve.


all the information is available in the trace. The problem is that sometimes you have to look for  Equinox Launcher and deeper to look for org.eclipse.equinox.launcher.

Path1:

From: Eclipse IDE for Java EE Developers 1.3.0.20100315-0831
To: org.eclipse.epp.package.jee.feature.feature.group [1.3.0.20100315-0831]
To: org.eclipse.platform.feature.group [3.6.0.v20100121-9hF78GK1FufosnFu87UwXZfHJWXovR-z-9b]
To: org.eclipse.rcp.feature.group [3.6.0.v20100201-9GAcFGCFq7Lo_y4ElaEbOXNc]
To: org.eclipse.equinox.launcher [1.1.0.v20100307]

Path2:
From: Eclipse Platform SDK 3.6.0.I20100429-1549 (org.eclipse.platform.sdk 3.6.0.I20100429-1549)
To: org.eclipse.rcp.configuration.feature.group [1.0.0.I20100429-1549]
To: org.eclipse.equinox.launcher [1.1.0.v20100419]

It would be better to represent the error using a graph, that way the problem would be easier to understand.

> > 2. Sometimes, the name of a plugin is used ("Equinox Launcher 1.1.0.v20100419")
> > and sometimes the plugin ID ("org.eclipse.equinox.launcher [1.1.0.v20100307]")
> > 
> > Either supply always both or only the name (which should be unique, right?)
>   The user readable name is shown for the IUs (along their id) and for the
> requirements we show the id because there is no user readable string there. We
> used to only show the id everywhere but users could not relate from the ID to
> the element they had selected in the UI.
> 
> I've renamed this bug to focus on making sure we show all the paths from all
> roots to the singletons.
Comment 5 Pascal Rapicault CLA 2010-05-08 10:02:46 EDT
I'll close that as a dupe of 261928 given that this is where we are working on improvements of error messages.

*** This bug has been marked as a duplicate of bug 261928 ***