Hi,
Both of the jst.server blocking bugs were incorrectly filed by the originator and have had their severity changed.
Thanks,
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503 (tieline 969)
[EMAIL PROTECTED]
| David M Williams <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 09/02/2006 11:51 PM
|
|
I think we forgot one step in our 1.0.1 end-game triage at status meeting today ... will component leads please address any "blocking" defects ... say, by Monday?
Either 1) say that you agree its blocking and should be fixed before 1.0.1 (and set target appropriately) or 2) work with the originator to have re-assigned to appropriate severity.
Thanks,
125711 2006-01-30 blo P3 [EMAIL PROTECTED] [EMAIL PROTECTED] NEW jst.j2ee --- Don't add all jspf in war file
126594 Mon 11:21 blo P3 [EMAIL PROTECTED] [EMAIL PROTECTED] NEW jst.serv --- Server launch configuraion and tab group are not extendab...
124097 2006-01-17 blo P3 [EMAIL PROTECTED] [EMAIL PROTECTED] NEW jst.serv --- Error: Could not load the Tomcat server configuration
124515 2006-01-19 blo P3 [EMAIL PROTECTED] [EMAIL PROTECTED] NEW wst.rdb --- Reserved keywords are wrong for most DBs
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
