Not surprisingly, I did have to disable
some features or repositories, such as
due to the usual "tight coupling"
that exists in them, to the exact version of the Eclipse platform;
and one project, not surprisingly, has
a tight coupling to JDT that will need some adjustment
What is a little different than usual,
is that I had to disable "rcp sdk" features ... for the simple
reason they weren't "built" for the 4.2 stream ... as its been
explained to me.
As far as I can see, no one in the Juno
"stack" depends directly on those particular feature packages,
but I mention this since some adopters may or some users may use them as
runtime targets. If so ... they'll need to wait for M2 (or ... talk to
the equinox/platform teams) ... see bug 354662.
A few other teams had to make some quick
fixes to quickly fit in to a few new pre-req versions, but overall, the
+0 day for M1 went very well using mostly the Indigo contributions as starting
point for the 4.2 based builds. Of course, we still have to test it running
together, but building, or aggregating together is a good first step. Please
install Eclipse 4.2 M1 and test with your own Juno contributions.
Next week, of course, everyone can/should
update to your official Juno M1 contributions, if you have them. If not,
you may want to update to your latest Indigo based build, if that's your
After all ... we are doing our Indigo
maintenance warm-up build next week too!
I did promote what we have so far to
.../releases/staging, mostly to test that our reports still get created
automatically ... and even that worked! See