Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and outlook for SR1 RC3 -- are we in trouble yet?

The Eclipse and Equinox features are consistent from my parsing of the metadata for the last few builds. However there is an older version of "org.eclipse.equinox.server.p2" being picked up by the aggregation that doesn't match what is in the latest platform build. I think we should be discarding our old builds that are still hanging around in our repository because somebody is picking them up. I'll chat with Kim about it.

David M Williams <david_williams@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

09/09/2010 12:19 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

[cross-project-issues-dev] Status and outlook for SR1 RC3 -- are we        in trouble yet?

Yes, I think we are in trouble. We haven't had a good build in two days. I'll admit Monday was a holiday for a lot of people .... but ... it's now Thursday ... +3 day!

I didn't pay much attention to the failures at first, expecting them to be fixed soon, but I think they may have all been similar to the latest one, see summary notice attached below or full console log at

It appears  that Eclipse platform and Equinox have some inconsistencies? (In a brief note from Kim, she thought it might be related to features losing their distinctive version qualifier suffix (bug 208143 and she was hoping "the next build" would fix that. Apparently not?

What scares me is once Eclipse/Equinox is fixed, I'm sure there will be several more issues, as there often is with Jetty and RAP having exact dependency versions ... hopefully they can react quickly, if that's still the case.

Plus, there's been no comment in bug 324419
which was blocking LinuxTools from contributing last week.

By all rights, if we are on day +3 and the day +0 contributions have not built yet, the whole schedule slips out 2 or 3 days.

I am hoping we can avoid that. Perhaps if we all get out of "holiday mode" and focus on the simultaneous release builds on Thursday we can recover? Let's assess schedule changes at the end of Thursday (or early Friday).

Thank you .... and good luck!

----- Forwarded by David M Williams/Raleigh/IBM on 09/08/2010 11:39 PM -----

David M Williams/Raleigh/IBM@IBMUS
Kim Moir <kmoir@xxxxxxxxxx>
David M Williams/Raleigh/IBM@IBMUS
09/08/2010 04:51 PM
[HeliosAggregation] Failed for build 2010-09-08_16-46-02

The following errors occured when building Helios:

Software being installed: 1.0.0

Only one of the following can be installed at once: [org.eclipse.equinox.p2.artifact.repository 1.1.1.R36x_v20100901, org.eclipse.equinox.p2.artifact.repository 1.1.1.R36x_v20100823, org.eclipse.equinox.p2.artifact.repository 1.1.0.v20100513]

Cannot satisfy dependency: 1.0.0 depends on: 3.6.1.r361_v20100903-7H7R07v8rtOZyYbv1I6aZgou5z07

Cannot satisfy dependency: 1.0.0 depends on: org.eclipse.sdk.ide 3.6.1.M20100908-0800

Cannot satisfy dependency: 2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr depends on: org.eclipse.equinox.p2.artifact.repository [1.1.1.R36x_v20100901]

Cannot satisfy dependency: 3.6.1.r361_v20100903-7H7R07v8rtOZyYbv1I6aZgou5z07 depends on: [3.6.0.v20100421-7u7NFVgFN5JdPKPhDHd_6Yqc54uw]

Cannot satisfy dependency: 1.0.0.v20100503-7x7IFGOFQ74dz0POCNUBj98N depends on: org.eclipse.equinox.p2.artifact.repository [1.1.1.R36x_v20100823]

Cannot satisfy dependency: 3.6.0.v20100421-7u7NFVgFN5JdPKPhDHd_6Yqc54uw depends on: [1.0.0.v20100503-7x7IFGOFQ74dz0POCNUBj98N]

Cannot satisfy dependency: org.eclipse.sdk.ide 3.6.1.M20100908-0800 depends on: [2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr]

Check the log file for more information:
cross-project-issues-dev mailing list

Back to the top