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

Bug 336417

Summary:	[releng] Use composite repositories
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	Releng	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	1.4
Target Milestone:	1.4 RC1
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralf Sternberg

2011-02-05 07:18:42 EST

We should consider using composite repositories, i.e. one single repository for every milestone or service release. The public repositories for tooling and runtime would then aggregate the content of the single repositories. This would help to solve problems such as:

* Rollback if we find problems after building a milestone. Once a build has been merged into a p2 repository is much harder to remove its artifacts.
* Keep SR RCs out of repos for a released version. Service releases should be added to the repos, but the SR RCs should not. Currently they are merged into our public repositories, which is bad.

There is a detailed discussion in bug 291637.

Comment 1 Ralf Sternberg

2011-05-18 04:30:53 EDT

*** Bug 344719 has been marked as a duplicate of this bug. ***

Comment 2 Ralf Sternberg

2011-05-18 04:35:45 EDT

Beginning with 1.4 RC1, the RAP repositories are now composite repositories that contain the real repositories as sub folders.
I created the composite metadata manually, following http://wiki.eclipse.org/Equinox/p2/Composite_Repositories_(new).
Next time we should consider creating them in an automated way or at least update the timestamp attributes to refresh caches.