We had a failed release last night apparently due to CVS connection
problems. Unfortunately it resulted in a partial release of the
code, which resulted in the compile failures. We're not sure why
the release tool didn't indicate a problem, so the release was
thought to be a success.
We have done a second release this morning which has been verified,
so next build should be in good shape.
Apologies for the delay. We were happy that our final release last
evening wasn't doing anything interesting (just a basic release of
some code changes), but of course doing something interesting in
this case wasn't required to break the build.
Neil
On 3/3/2011 9:26 AM, David M Williams wrote:
There was a compile
error in latest build,
no unit tests ran and a fair number of changes from previous
build. So,
I think we need to wait for a new build before smoke testing a
build to
declare these week.
It appears the compile error was
caused
by org.eclipse.jpt.common.core not being released ... or, I
suppose, org.eclipse.jpt.jaxb.ui
was released too soon? (That is, org.eclipse.jpt.jaxb.ui
requires some
changes recently added to org..eclipse.jpt.common.core. [I
looked ... since
from the compile error, I thought something was wrong with ICU
dependencies].
I'm sure this will be corrected
soon,
and we'll have a new build this afternoon.
Thanks,
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
|