No...it's not a compile-time issue, so a respin isn't absolutely
necessary. We can declare without it.
Neil
David M Williams wrote:
Is a literal re-spin really needed
before
we declare? That is, is it a compile-time issue? Or, can we possibly
declare
with a note saying to be sure to use the more recent DTP?
The base DTP bug related to this regression has been
fixed.
They are respinning a DTP build now. Once it is complete (ET
is before 2pm), we will want to respin to pick up the change.
Verification
can then be performed and we should be able to declare, assuming other
action items have been resolved.
Neil
Neil Hauge wrote:
JPT has failed its smoke test. A recently released
change in DTP has caused a major regression in the JPT functionality.
See
bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=204195
for more details.
We either need DTP to revert the change, or we need to work around the
change ourselves. The code was released in the 9-12 DTP build, but
was not caught last week due to the problem not presenting on the
hardware
that the smoke tests were run on.
Neil
David M Williams wrote:
1. 204203 Severe regression in JSPModelProcessor
Needs PMC review and to be dropped to a build.
2. http://wiki.eclipse.org/WTP_Smoke_Test_Results_R20
most teams still need to do or document smoke test results
Our goal is noon (Eastern)
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
|
