Re: [wtp-dev] Status of M3 build -- two problems suggest a rebuild is in

[Chris Brealey <cbrealey@xxxxxxxxxx>]

 +1

The Web Services Explorer is just too
cool (IMHO) to leave out!

Cheers - CB.

Chris Brealey
Rational Studio Java Web Services, IBM Canada Ltd.
D3-275, D3/ENX/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada,
L6G 1C7
cbrealey@xxxxxxxxxx, 905.413.6038, tieline:969.6038, fax:905.413.4920

David M Williams <david_williams@xxxxxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx

02/25/2005 02:46 PM

Please respond to
wtp-dev

To	wtp-dev@xxxxxxxxxxx
cc
Subject	[wtp-dev] Status of M3 build -- two problems suggest a rebuild is in order.

We've discovered two problems with current candidate build for M3. See

https://bugs.eclipse.org/bugs/show_bug.cgi?id=86662

https://bugs.eclipse.org/bugs/show_bug.cgi?id=86683

One is strictly a build script problem between I and S builds, that was
discovered 
in routine integrity checking. Its is serious, though, in that web services
explorer won't work in "runtime" (non-SDK) version. Technically,
could be fixed 
by patching download zip, but we're rather be pure about 
it and have a "reproducible build". 

The other is a regression on setting breakpoints in JSPs ... you can do
it once just 
fine (the normal extent of my quick testing) but not again unless you close
workbench 
and restart. Thanks to Phil for continuing to test and finding this problem
that 
would interfere with users "getting work done". (That is, I don't
think we could 
claim JSP breakpoints, if you can set only once). The fix is safe and simple
and 
would not impact anything else. 

If there's no objections, I'll request a rebuild once we confirm scripts
and 
release fix. Teams would not have to re-test (except JSP breakpoints) 
and I will repeat my integrity checks.