Update.
Earlier today the Planning Council has given the go to include the fix
in the release train.
A platform build has been done, and it has been confirmed that the
problem has been fixed. The build number is M20140221-1700.
Once the execution of the automated tests completes, David will
p
Based on feedback from the Planning Council, I will do a "rebuild" of the
aggregation repository, once the fixed version of p2 is available and
verified.
I thought I'd be explicit that my plan is to do the sort of rebuild where
the input from all other projects is simply taken to be what alrea
Hi,
This is a heads up that a pretty bad bug has been discovered in p2 which
can leave an installation in a non startable state
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=428575).
This does not happen on every install. It only occurs when the import
wizard triggers the remediation, but i
It's sufficient to add both provided p2 repository URLs to the list of
available software sites (preferences > install/update > available software
sites):
http://build.eclipse.org/technology/epp/epp_build/kepler/download/20140220-0320/repository/
http://download.eclipse.org/releases/maintenance/
David,
I'd like to test
>...at least that "SR1" levels can be updated to "SR2" ... and to do that
you might need to (re)read ..
...But I can't find enough info on the referenced links that says how to
assemble a "pseudo composite" to test updating e.g. from SR1 to SR2. It
says to look in epp-dev.
I'm sure everyone knows that final builds are done ... but we always wait
a week before formally releasing. This is partially to give one last
chance to test for serious regressions. (If found, In most cases, we'd
encourage projects to simply provide "patch features" on their own sites,
if poss
