Hi David,
I've tracked the problem down, and it is due to a change in the module versions returned from jst.j2ee. In previous weeks the status quo was to return the J2EE spec version (e.g. 1.4) even at the module level, but this week it has changed to the actual module spec level (e.g. 2.4). As a result, all existing server adapters are unable to run the module. We can discuss what the correct implementation is later, but if we want to declare an I-build today we'll have to change this back instead of trying to change all of the server adapters to match.
I've transferred the bug to jst.j2ee for further investigation, and Chuck's team is already looking at it.
Thanks,
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503 (tieline 969)
[EMAIL PROTECTED]
| David M Williams <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 10/14/2005 12:36 PM
|
|
yet, at least.
I've been unable to "run on server" using Tomcat (to test a JSP, and test debugging).
I've been unable to find anyone who can (in the 3 minutes I've tried).
I've opened "blocker"
https://bugs.eclipse.org/bugs/show_bug.cgi?id=112655
So ... I'll wait until component leads chime in and tell me its just me,
or ... provide a fix! I'll refrain from declaring this weeks I-build, since this
problem (if it is) seems it would interfere with further developement.
Chuck, Tim, Others? Has anyone been able to do this?
Which any server?
Or, can you confirm it is a bug?
Feel free to use bug 112655 to comment on findings.
Committers .. please remember not to release anything until declared .. in case
we need to re-spin, we don't want to risk breaking anything else.
Thanks,
_______________________________________________
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
