most of Web Services and portions of
J2EE tools will not be in the 2/10 I-build. There are a few final bits
of integration work being done now, and which will be introduced into HEAD
in the next day or two. Everything should be in the following week's (2/17)
Web services function in M3 will consist
mainly of wizards for building, deploying and testing Apache Axis 1.1 Java
(not EJB) Web services (bottom-up and top-down) and clients on various
Apache Tomcat servers. With a bit of luck, M3 may also include the infamous
Web Services Explorer. For more information please see the WST Web Services
 and JST Web Services  M3 milestone plans.
Rational Studio Java Web Services, IBM Canada Ltd.
D3-275, D3/ENX/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada,
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/08/2005 10:54 PM
Please respond to
[wtp-dev] Upcoming important
dates for WTP M3
Its that time of the cycle again, so thought I would explicitly summarize
discussed and written in many different talks and notes and plans.
2/10 - Thursday - regular I-build ... most teams are planing to have all
function "in the build" by this I-build
(its no show-stopper if not there, but, if
not there, a note to this list would
help keep everyone aware of status and last
minute changes still coming).
2/11 - Friday. move up to latest Eclipse M5 I-build, and "all the
latest" of GEF,
EMF/XSDInfoset, and JEM.
(early peeks indicate there will be roughly
42 compile errors when we first move
up, so several teams have some work to do).
2/18 - Friday, Final Test Plans and new mini-tutorials for new function
Milestone, from each component team (please
update previous tutorials where
changed, include some regression testing on
but focus on new function just added -- and
remember, no need to wait until this
final deadline if you can provide earlier!).
2/18 - Friday - Final Eclipse M5 due
2/19 - Saturday, move up to final M5 and pre-reqs (can build team can work
if so, I suggest one person from each component
team be available on weekend to
keep them company, and sanity test the results,
to be sure there's
no serious issues that would prevent further
final testing during the week)