I have updated EclipseLink for Juno. I doubt there will be issues,
but this is the initial contribution, so wanted to give a heads
up... especially since you are already having issues.|
I will be keeping an eye out for any aggregation emails... when do
you expect the next run?
On 21/09/2011 10:54 PM, David M Williams wrote:
Well, no, probably
not ... but, it will
take a lot of attention to get it done on time.
First greatest thanks to Kenn
for making (or fixing) an "early" contribution repository 
for EMF core (or, "base", I think they are now calling the
This allows Eclipse 4.2 M2 and
to both be installed from repository sites. (For full issues,
term improvements, you can follow bug 356644).
Now the problem is that the new
of EMF (and maybe Eclipse M2?), apparently, breaks numerous
contributions, apparently due to increased minor version numbers
with narrow ranges?).
To aggregate, at the moment, I
have to disable about 20 of the b3aggrcon files in
I can (and may) do some
but, thought it would be a good time to review the process and
making contributions to an aggregation build:
you do not have to wait until
day to make a contribution. You can make a "warm-up"
at any time ... especially if it is needed to allow the
succeed. In other words, your +n day is the last possible day to
contribution ... not the first day you may make one.
Many of the current problems are
effects" from a few low level, commonly used bundles or features
modeling projects, it appears) so, maybe with only a few fixes
on the right path again, but, I ask that teams try to respond as
as possible to fix any "aggregation errors" they get notified
about ... please do not think you can wait until your final
next week ... and even if you have not been notified yet, if you
please "peek ahead" with the M2 versions of Eclipse and EMF base
and prepare an early version, even if you re-contribute your
during the (final) window next week. After all, if we had to do
"iteration" waiting for each of 20 project to fix their builds
sequentially before the next one fixes theirs, then we will not
Thanks, for your attention, let
if questions or issues.
cross-project-issues-dev mailing list