Community
Participate
Working Groups
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
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.
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.
I see ... wrong feature in title. org.eclipse.net4j.sdk.feature.group
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?
(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.
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.
Well, in fact aggregation #188 did fail, but I can not see that my contribution is causing this. Correct?