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

Bug 226757

Summary: Support association of p2 repositories
Product: [Eclipse Project] Equinox Reporter: John Arthorne <john.arthorne>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: 3.4   
Target Milestone: 3.4 M7   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 223981    

Description John Arthorne CLA 2008-04-11 16:36:25 EDT
There should be a way for a p2 repository to specify an association with another repository (either of the same type or a different type). Update Manager had a similar notion of "associate sites" but we can't use that existing mechanism exactly as it is, since it doesn't support the notion of different repository types (metadata vs. artifacts).

One interesting property of UM associate sites is that there is a level of indirection. A site just referenced an "associate site URL", which was the URL of an XML document that provided a list of associated sites. Thus the exact set of associated sites was computed at runtime and could be changed by an administrator independently from the referring site.  I don't know if we need a similar level of indirection in p2 associated repositories.
Comment 1 John Arthorne CLA 2008-05-08 16:59:38 EDT
This was implemented in 3.4 M7. See IMetadataRepository#addReference.