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

Bug 221698

Summary: Update site fails to install due to incorrect paths
Product: [Eclipse Project] Equinox Reporter: Andrew Niefer <aniefer>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: simon_kaegi, tim-at-eclipse
Version: unspecified   
Target Milestone: 3.4 M6   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Andrew Niefer CLA 2008-03-06 12:59:40 EST
Starting with a p2 enabled sdk, add the update site
"http://download.eclipse.org/tools/cdt/releases/europa"

Install the CDT Main Feature "Eclipse C/C++ Development Tools" (4.0.3.200802251018).  The install fails with messages like:
      
error during transfer
        Exception connecting to http://download.eclipse.org/tools/cdt/releases/plugins/org.eclipse.cdt.launch_4.0.3.200802251018.jar.
     http://fullmoon.ottawa.ibm.com/tools/cdt/releases/plugins/org.eclipse.cdt.launch_4.0.3.200802251018.jar

Note that the path is incorrect, the actual path is 
.../cdt/releases/europa/plugins/...

The "europa" path element is being lost.  The same occurs when using a local update site.

Note that using "http://download.eclipse.org/tools/cdt/releases/europa/site.xml" works.
Comment 1 Simon Kaegi CLA 2008-03-06 13:04:24 EST

*** This bug has been marked as a duplicate of bug 219904 ***
Comment 2 Timothy Webb CLA 2008-03-06 13:11:30 EST
I don't believe this is the same bug as the one it was duplicated against.  In looking at the report, it looks like the new logic to try and guess the location to the site.xml is incorrectly appending the paths.  Note the loss of the "europa".  I don't believe this issue has to do with archive paths.

Also, in looking at the site.xml, there are no archive paths defined for the CDT site.
Comment 3 Simon Kaegi CLA 2008-03-06 14:06:19 EST
Thanks Tim. You're right this has nothing to do with archive URLs.
In this situation both the plugins and features URLs were calculated incorrectly if the base URL didn't end in either "/" or "site.xml".
Fixed in HEAD.