Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] DTP for Neon stream ... runtime.compatibility ... and LDT? ... and Neon M2

I hope everyone remembers that Neon M2 is this Friday ... and that means your Neon M2 contributions must be done by Wednesday.

AND .. it seems, some have not yet reacted to the platform removing org.eclipse. runtime.compatibility bundle (Bug 394739).

AND .. some have been "getting it automatically" from the current Sim. Release contributions, because Lua Development Tools (LDT) duplicates it (and many others) in their repository (Bug 478009).

Since LDT has not updated their repo yet for Neon, I fear some may have of a false sense that "everything is ok".

Put more bluntly, we all know, some projects do not build against the latest version of their pre-reqs! And, we all know that some projects won't react until "the build fails".

Therefore ... I am about to make the build fail for others, by removing LDT's massive contribution.

If someone has a better suggestion, that would be good to hear, but I hope I am doing everyone a favor, by making the problem more apparent in the aggregation build.

(And, greatest thanks to those of you who HAVE reacted to this change already ... thanks to all your release engineers!)

Thank to you all,

From:        David M Williams/Raleigh/IBM@IBMUS
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        09/21/2015 08:09 PM
Subject:        Re: [cross-project-issues-dev] DTP for Neon stream ... and LDT?
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

> A question regarding the aggregation build. I thought it was
> designed to catch issues like this, but I don’t see any failures on Hudson.

I was wondering that too. :) So ...

I looked in the log, at
and could see

- mirroring artifact osgi.bundle,org.eclipse.core.runtime.compatibility,3.2.300.v20150423-0821

and then searching backwards in log, for "Mirroring artifacts from",
could see that the LDT project is (also) contributing that bundle, via their repository at


I hope that is a temporary condition, since (in this case) do not think the Platform would like others
"extending the life" of something they are trying to end. But ... I am not sure. I think the next step
is to hear from the LDT project. I have opened
bug 478009 for this issue.

I did also use b3 aggregator editor to search for others who might be contributing that bundle, and it appears there are no others.
(And, appears that LDT contributes much more potentially problematic bundles, than just that one, since they duplicate a great deal
of other's projects, for their "Eclipse product").

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top