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

Bug 312984

Summary: [repository] Composite repo should have the ability to be marked in error if a child repo is bad
Product: [Eclipse Project] Equinox Reporter: Pascal Rapicault <pascal>
Component: p2Assignee: Katya Stoycheva <katya.stoycheva>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 3.6   
Target Milestone: 3.7 M7   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Attachments:
Description Flags
Composite repository atomic loading support none

Description Pascal Rapicault CLA 2010-05-14 17:39:11 EDT 
In some cases the composite repo really needs to have all its children enabled and properly loaded to be useful. In other cases this is not necessary.

Composite repo should have a flag to indicate which behaviour they like.

In the failing mode the error should be reported to the user on the composite repo.
Comment 1 Katya Stoycheva CLA 2011-04-21 12:52:27 EDT 
Created attachment 193860 [details]
Composite repository atomic loading support

Composite repository (both Artifact and Metadata) now have a flag "p2.atomic.composite.loading" to indicate whether a failure while loading any of its children should result in failure in composite repository loading.
The default value is false.
If composite repository fails to load and the flag above is set to true all the children loaded on the behalf of the composite repository will be removed from the repository manager. If some of the children have already been available before loading of the composite repository they won't be removed.
Comment 2 Pascal Rapicault CLA 2011-04-21 14:27:18 EDT 
I've reviewed this patch and applied it. The code is really clean and properly tested. Thx for working on this.