Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316232 - org.eclipse.net4j.sdk.feature.group has been blocking builds for 6 hours
Summary: org.eclipse.net4j.sdk.feature.group has been blocking builds for 6 hours
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Cross-Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Cross-Project issues CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-08 22:22 EDT by David Williams CLA
Modified: 2010-06-09 04:37 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2010-06-08 22:22:14 EDT
Missing requirement: all.contributed.content.feature.group 1.0.0 requires 'org.eclipse.net4j.sdk.feature.group 3.0.0.v20100608-1558' but it could not be found

Check the log file for more information: https://build.eclipse.org/hudson/view/Repository%20Aggregation/job/helios.runAggregator/177/console
Comment 1 David Williams CLA 2010-06-08 22:31:31 EDT
I guess I don't need to say how disruptive this is? 

The version in the emf-cdo file says 

3.0.0.v20100608-1558

the version in the content.jar/xml file for the IU says

3.0.0.v20100604-1150 

Since Eike will be asleep for several more hours, at least, I'm going to blindly put in the value I find in the content.xml/jar file ... and see what happens. Could not get much worse.
Comment 2 David Williams CLA 2010-06-08 22:45:07 EDT
Second try ... after that failed I looked again and must have been looking at wrong feature group ... conent.jar/xml says
3.0.0.v20100531-1052

Next trial and error will be just to remove the contribution completely. See who else depends on it.
Comment 3 David Williams CLA 2010-06-08 22:47:35 EDT
I see ... wrong feature in title. 

org.eclipse.net4j.sdk.feature.group
Comment 4 David Williams CLA 2010-06-08 23:06:07 EDT
well, I ended up back leveling each feature in the contribution file. Perhaps a build was expected to be promoted but didn't? Perhaps the URL for the repository is wrong? 

I'm sure my changes are not really correct for what's intended, but at least build is getting to the next phase so other aspects of many other peoples contribution can be tested. 

For future reference, what else in helios does depend on these features?
Comment 5 Nicolas Bros CLA 2010-06-09 04:26:14 EDT
(In reply to comment #4)
> For future reference, what else in helios does depend on these features?

MoDisco (more precisely org.eclipse.gmt.modisco.java.discoverer.cdo) depends on org.eclipse.emf.cdo.net4j, which in turn depends on org.eclipse.net4j.
Comment 6 Eike Stepper CLA 2010-06-09 04:36:00 EDT
Sorry for this new hazzle. I already explained in the mailing list how this was obviously caused by using the slave build server. I just verified that my fix caused no new failure, so I'm resolving this bug as FIXED.
Comment 7 Eike Stepper CLA 2010-06-09 04:37:50 EDT
Well, in fact aggregation #188 did fail, but I can not see that my contribution is causing this. Correct?