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

Bug 368050

Summary:	Indigo SR2 b3aggrcon file out of date
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	kim.moir
Version:	3.7.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2012-01-06 13:09:07 EST

The indigo SR2 aggregation build is currently breaking with 

Unable to load repository p2:http://download.eclipse.org/eclipse/updates/3.7.x/M20110909-1335

This is simply "out of date" and the M20110909-1335 build removed (or archived?). 

Unless I hear otherwise, soon, say ... in 15 minutes or so? :) ... I would fix this by updating the URL to point to the latest M build, 

M20120104-0800

But, this will require either updating the "feature versions" mentioned in the b3aggrcon files, or ... my suggestion ... just leave out the version numbers. This later technique is feasible as long as the repository URL contains one and only one version of features desired to be contributed. (If it contains more than one, it can still be used, and the aggregator (p2) will simply "take latest", but that is less explicit, so is not recommend, by me). 

In theory, this could maybe also be fixed by using 
http://download.eclipse.org/eclipse/updates/
or something, that presumably would still have the old (released) versions ... but as far as I know there is no reason not to "get current" and it would simply be a preview of what's coming next week, when the file is updated for RC1 warm-up. 

Let me now, quick, if you'd rather fix this yourself. 

Thanks,

Comment 1 David Williams

2012-01-06 13:21:32 EST

Hmm, this might be more complicated than I thought ... when I tried to use latest build URL

http://download.eclipse.org/eclipse/updates/3.7.x/M20120104-0800

it says (in my local workspace build) there is no 

org.eclipse.pde.api.tools.ee.fragments.feature.group

I'll disable that one feature, for now, ... I doubt any has a direct dependency on it ... but, that will be something you'll have to fix (as I do not know about it ... is that something you add in a separate step? Or is your M build broken?).

Comment 2 David Williams

2012-01-06 13:37:59 EST

I have "fixed" as I have indicated above, and build is progressing. 

But, I'll leave open so you can fix as you'd like, and address the issue with the missing 

org.eclipse.pde.api.tools.ee.fragments.feature.group

(or, I'll let you open a separate bug for that, if that's a large or surprising issue).

Comment 3 Kim Moir

2012-01-06 14:51:13 EST

Hi David

Sorry for the delay, I was working on making the 4.2 build primary and didn't check my email for a while.  

The pde.api tools issue is bug 362103

Comment 4 David Williams

2012-01-06 19:51:59 EST

(In reply to comment #3)

> 
> Sorry for the delay, I was working on making the 4.2 build primary and didn't
> check my email for a while.  
> 
> The pde.api tools issue is bug 362103

NP. Let's count this one as "fixed" then, since the "missing repo" problem is now fixed, 
bug 362103 will track the missing feature, 
and you can update next week (on or before 1/13) for RC1 however you see fit. 

Thanks.