Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336417 - [releng] Use composite repositories
Summary: [releng] Use composite repositories
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: Releng (show other bugs)
Version: 1.4   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 1.4 RC1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 344719 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-05 07:18 EST by Ralf Sternberg CLA
Modified: 2011-05-18 04:35 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Sternberg CLA 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 CLA 2011-05-18 04:30:53 EDT 
*** Bug 344719 has been marked as a duplicate of this bug. ***
Comment 2 Ralf Sternberg CLA 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.