OK, ready to try again? Since the LDT contribution
has not changed, I have disabled it from the aggregation build, so that
we can see who else still refers to the defunct compatibility runtime bundle.
According to my local builds, BIRT will
be the next project to fail ... now that DTP has been fixed (thanks Konstantin,
and others). [Correction
Please correct any failures as soon
as possible. That is, don't wait until your +N day. You can always contribute
your final content later, but build "breaks" should be corrected
Same goes for you, LDT team, though
I know your "break" isn't obvious, and realize you have some
"redesign" work to do to figure out how to deliver "just
your code" (and not all dependencies too).
David M Williams/Raleigh/IBM@IBMUS To:
Cross project issues
09/30/2015 11:04 AM Subject:
DTP for Neon stream ... runtime.compatibility ... and LDT? ... and Neon
M2 Sent by:
OK, I give up.
It appears some projects are not going to be able to react to the removal
of runtime.compatibility bundle, for M2, so I have re-enabled the LDT contribution.
478009 and Bug
478330). This will allow the aggregation build, at least, to complete, so that others
can make progress.
This won't help projects who have a direct dependancy on, say, DTP (which
in turn as a dependency on runtime compatibility bundle) since they depend
on it, but do not provide it. For those people, the only work around I know of is to "include"
only that bundle from our M1 repository, or something similar. Less that ideal, but I'd like to push forward and see if we can get out
some form of M2 that can be used to create a cleaner M3!
Let me know if suggestions or alternative approaches. (And, FYI, it does
not appear that extending the deadline a few days will help with the runtime
compatibility issue, but, if anyone has been blocked due to this issue,
and needs a few days to work around the problem, I think it reasonable
to consider an extension of a few days ... if you make such a request,
please be specific ... I'd hate to extend it to Monday instead of Friday
(let's say) and then that still not be enough time.)
M Williams/Raleigh/IBM@IBMUS To: Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>, Date: 09/28/2015
08:47 PM Subject: Re:
[cross-project-issues-dev] DTP for Neon stream ... runtime.compatibility
... and LDT? ... and Neon M2 Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
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
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
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
(And, greatest thanks to those of you who HAVE reacted to this change already
... thanks to all your release engineers!)
Thank to you all,
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
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 .../download.eclipse.org/ldt/releases/stable/1.3
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").