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

Bug 358704

Summary: does 'contact' need to be two-way "reusable" element of model?
Product: [Technology] CBI Reporter: David Williams <david_williams>
Component: CBI p2 Repository AggregatorAssignee: CBI Inbox <cbi-inbox>
Status: CLOSED WONTFIX QA Contact: David Williams <david_williams>
Severity: enhancement    
Priority: P3 CC: frederic.gurr, thomas
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Williams CLA 2011-09-23 06:19:28 EDT 
I know from experience, one of the most frequent "user errors" made in updating aggregator models for the yearly Simultaneous Release is that people add or remove the "contacts" element in their b3aggrcon file, but forget to (or, do not know to) update with the model editor, so that the change is made in both the main file (simrel.b3aggr) as well as their projects b3aggrcon file. 

Is it really required to define the model this way? Or is there some use-case I'm not aware of? Seems it would be easier if indeed users could just update their b3aggrcon file, instead of having to touch the main file, just to change a contact person.
Comment 1 Thomas Hallgren CLA 2011-09-23 08:13:19 EDT 
The general idea was that the set of contacts was managed globally for the aggregation and that each contribution then could select from that global set. I agree that this is a bad fit for the release train use case where the contributions reside in separate files.

It should be easy enough to change so that the contact is contained in the contribution rather than referenced and add a compatibility layer. Once we do, we must ensure that all b3aggrcon files are changed simultaneously since the change will affect their content as well as the master.
Comment 2 David Williams CLA 2016-09-16 15:43:03 EDT 
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.]
Comment 3 Frederic Gurr CLA 2023-09-01 10:04:15 EDT 
If this issue is still relevant, please move it to https://github.com/eclipse-cbi/p2repo-aggregator/issues.