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

Bug 329652

Summary: several validation problems due to Jetty Contribution
Product: Community Reporter: David Williams <david_williams>
Component: Cross-ProjectAssignee: David Williams <david_williams>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
log from recent failure that shows the type of errors none

Description David Williams CLA 2010-11-08 00:48:20 EST 
I'm opening this in cross-project even though I think immediate problems are Jetty specific, in order to get everyone to focus on the overall process, and making sure their contribution files are correct. 

A. I guess I missed a notice message, but with the current indigo failures, a note is not sent to the specific team that "caused" the problem. So, partially my fault. But ... honestly ... when you contribute something to the common repo aggregation, do not take absense of a failure note to mean your contribution was succesful ... check every now and then?! Especially when changing "contributors" and/or "categories" ... common breakage points. (I've opened bug 329651 to see if Aggregator could be improved). 

B. Please install the Aggregator editor and make changes to contributors and categories using it. When you change these "objects" there are two files that need to be updated. Very hard to do "by hand". 

I'll look at the current problems and see if I can guess a fix.
Comment 1 David Williams CLA 2010-11-08 00:53:01 EST 
Created attachment 182586 [details]
log from recent failure that shows the type of errors
Comment 2 David Williams CLA 2010-11-08 01:22:57 EST 
Hmmm, now I'm confused. The jetty contribution files look (relatively) correct, at least with respect to "contacts". 

Even more confusing, when I first loaded up all the latest stuff in Aggregator editor (sync'd with head) and then did a "validate", I saw the same errors in my workspace as is showing in the build logs. But then (the confusing part) after about 10 or 15 minutes (no changes to indigo build files) it started showing some other errors (some simple "features not found in repository) type messages. 

So ... something's odd. Perhaps the build is getting "old" input, somehow. (among other things). Now it is truly a cross-project bug :/
Comment 3 David Williams CLA 2010-11-08 01:29:50 EST 
Oh, well, I partially take that back ... I did find 

'hmalphettes@intalio.com' 

had an extra space at the end, 

'hmalphettes@intalio.com '
in the main indigo.b3aggr file, but the jetty.b3aggrcon did not have that extra space (any longer ... it did in previous version). 

Very hard to spot. 

And, not sure why Aggregator editor "saw" it, then didn't? Guess it was as confused as I am.
Comment 4 David Williams CLA 2010-11-08 01:50:58 EST 
I've "fixed" the immediate problem by removing some stuff from categories and even the contribution. Is there really a "bundles.f" feature group? "f" isn't very descriptive, even if it is just a symbolic id :) 

And seemed it didn't exist in repo, at least not at that version. 

And, seemed some new "category" was made, just for Jetty? And was part of "general purpose tools" as well as "runtime targets"? 

So ... I'll let the Jetty team sort that out. I always like doing categories, after the build is working :) It is building now ... we'll see if it completes as is ... if so, feel free to fix the categories, and/or open a new bug here if you'd like my help. 

Thanks, 

Oh, and I think I figured out the confusion over "validate". I think it only works if the main "Aggregator Indigo" node is selected. I think I hit "validate" sometimes, when some other node was selected and it didn't really validate the whole model (if any). It did give accurate messages when I had that node selected. Sorry for the confusion.