Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Status of WTP 1.5 RC1 ++

Well .. its nice to know at least one person reads my long notes ... my long notes (she reminded me)  about me not communicating well  :)

The sentence
        (Oh, and don't forget to well-test items that might be effected by us newly including the
was meant to be
        (Oh, and don't forget to well-test items that might be effected by us newly including the org.eclipse.equinox.servlet.api bundle

This would mostly be Web Services Explorer,  JSP Editing around taglibs, but ... I'll also be interested if there's any new classpath complications
when "run on server", etc. (shouldn't be .. I'm just saying I'll rest easier after Tim says there isn't :)


David M Williams/Raleigh/IBM@IBMUS
Sent by: wtp-dev-bounces@xxxxxxxxxxx

04/20/2006 04:45 AM

Please respond to
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>

[wtp-dev] Status of WTP 1.5 RC1

What? What's RC1? Enough people have been asking me, I realize I haven't done a very good job of communicating ...
There has been a little "clarification" of the Callisto schedule, and it was decided everyone needed a "quick RC1",
and then subsequent "due dates" would have a narrowing gap. These are listed in the Callisto plan

and I've pasted the next few at the bottom of this note.
(Someone, besides me, I'm assuming will be update our WTP web pages to clarify).

So, yes, our weekly I-build this week will be "RC1" ... based on Eclipse RC1 .... well, actually RC1a, once its ready.

So, for you early risers, there's no harm in getting the recent RC1 candidate build, and shaking it out some, especially if you haven't been already,
but, we still need to upgrade to RC1b and RC1 of all our pre-reqs.

There will be some issues if you do anything HTML related, but that will be fixed if you run on RC1b (no need to wait for a re-compile to run and test on RC1b).
(Oh, and don't forget to well-test items that might be effected by us newly including the

But ... there's another blocker ...  sort of ...

I do not think this would be evident with "end users" using the build, but,
it does prevent our JUnit tests from running --- and as sparse as they are, we need
them to run (and pass!)  to declare a build!  

So, 3 options,

1. We could do our builds/tests with a "patched" build, to fix 136970 (and before you ask, we've already gotten an RC1a ... let's not push our luck :)

2. We could all add
ErrorDialog.AUTOMATED_MODE=true to the 'setup' method of our UI related JUnit tests (we should do that anyway, but
not sure how much time/effort it will be, and not positive it will easily and completely work-around this particular problem).

3. Jeffrey ... ? Do you still have those automatic cascading tests running? Maybe we could live with a Windows test?

Or, heck, guess "4."  I could X-Windows to the test machine and keep clicking  "Yes" now that Naci's showed me how :)  

Bottom line, I do not think we will be ready to "smoke test" until late Thursday, and/or early Friday ... but, it is still important we declare by noon on Friday
(keep that train a' chug'n).  So, do feel free to say if you think this impossible, but otherwise, let's plan on that. I'm sure we'll have an update by the 2:00 status meeting.

Just wanted to let everyone know what I know.


= = = =

RC1 (14-Apr .. 21-Apr)
  • 14-Apr - Platform
  • 19-Apr - CDT, DTP, EMF, GEF, VE
  • 21-Apr - BIRT, GMF, TPTP, WTP
RC2 (28-Apr .. 5-May)
  • 28-Apr - Platform
  • 3-May - CDT, DTP, EMF, GEF, VE
  • 5-May - BIRT, GMF, TPTP, WTP
RC3 (12-May .. 19-May)
  • 12-May - Platform
  • 17-May - CDT, DTP, EMF, GEF, VE
  • 19-May - BIRT, GMF, TPTP, WTP

wtp-dev mailing list

Back to the top