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

Bug 363054

Summary: Libra breaking Juno Aggregation due to incorrect model
Product: z_Archived Reporter: David Williams <david_williams>
Component: LibraAssignee: Project Inbox <libra.general-inbox>
Status: NEW --- QA Contact: Kaloyan Raev <kaloyan>
Severity: normal    
Priority: P3 CC: ccc
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Williams CLA 2011-11-07 10:22:05 EST 
The last couple of Juno Aggregation builds have "broken" due to contribution in webtools.b3aggrcon file. Perhaps the matching simrel.b3aggr file was not committed? 

This type of breakage, when model is broken, prevents email notifications from being sent, hence this bug report.
Comment 1 David Williams CLA 2011-11-07 10:23:25 EST 
Adding Carl, since "webtools problem" ... even though fairly obvious this was from Kaloyan's checkin.
Comment 3 David Williams CLA 2011-11-07 14:35:18 EST 
I "fixed" this by simply removing the "categories" element from the new addition: 

    <features name="org.eclipse.libra.framework.editor.feature.feature.group">
      <categories href="simrel.b3aggr#//@customCategories[identifier='Web%2C%20XML%2C%20Java%20EE%20and%20OSGi%20Enterprise%20Development']"/>
    </features>

If in fact that is the right thing to do and the categories element was not intended to be there, then please close as fixed. 

If instead you did want that feature to show up among all the other many features in that category, then I'll leave open so you can categorize as desired (and don't forget to commit changes required in simrel.b3aggr. 

If you need help, let me know.
Comment 4 Kaloyan Raev CLA 2011-11-08 03:41:31 EST 
David, the intention was to include this feature in the category. 
I submitted another patch - hopefully it's all correct now. I've executed Validate Aggregation - it shows no problems with Libra contributions.