Community
Participate
Working Groups
Created attachment 114809 [details] Error log Executing smoke test for http://build.eclipse.org/webtools/committers/wtp-R3.1-I/20081010055538/I-3.1-20081010055538/ Smoke test is http://wiki.eclipse.org/J2EE_Smoke_Test_(WTP_3.0) On the first Create Web 24 project step. I am starting the Dynamic Web Project errors are logged in the error log. Will attach the error log.
There are a number of exception for wst and for jst. But for jst they are more so I am setting in J2ee Standard Tools component
The Error Log suggests that the JSDT plug-ins haven't been included in the test Eclipse, or for some reason, they aren't running. Specifically the "wst.jsdt.web" facet declared in the plugin.xml from org.eclipse.wst.jsdt.web.core plug-in has not been registered. I believe all of the errors in the log are a side effect of that. I've checked the <facet> element for org.eclipse.jst.server.tomcat.core and it has the required id attribute, whose value happens to be "wst.jsdt.web". I'm not seeing this problem in my test environment using the I-3.1-20081010055538 build. Specifically, I'm using the wtp-sdk zip.
Oops, spoke too soon. I am seeing this problem with this build once I try to create a dynamic web project. Closer inspection shows that the facet declaration for "wst.jsdt.web" has been commented out per Bug 243183. Some changes for Bug 221928 may need to be redone.
Executing the smoke test for http://build.eclipse.org/webtools/committers/wtp-R3.1-I/20081030163955/I-3.1-20081030163955/ and verifying that the problem is reproducible.
Executing the smoke test for http://build.eclipse.org/webtools/committers/wtp-R3.1-I/20081120084906/I-3.1-20081120084906/ and verifying that the problem is reproducible.
While this is ugly and needs to be fixed ASAP, I do not think .log errors with no runtime failure qualify as "major" and am lowering severity. There are two separate issues in the .log here: Brad - Based on comment #3 and the associated bugzillas, it looks like the JSDT facet was backed out?? Please let me know if I should back out the changes made in bug 221928. Konstantin - Can you confirm that 'id' was made a required attribute of the facet extension points in 3.1? If so, I'll fix the server extensions.
> Konstantin - Can you confirm that 'id' was made a required attribute of the > facet extension points in 3.1? If so, I'll fix the server extensions There used to be a problem in the logging code for this error scenario that caused bogus messages to be logged. The problem it is trying to report has nothing to do with the missing id attribute. The logging code has since been fixed to log the correct "facet not defined" message.
Fine, the error message in the log is fixed in the latest I-build. Now, it is full with "Project facet wst.jsdt.web has not been defined. " Let's find the reason for this. Brad?
*** Bug 262098 has been marked as a duplicate of this bug. ***
Fixed, or at least no longer happening?
Yes, this was fixed via bug 263865 adding the facet back. *** This bug has been marked as a duplicate of bug 263865 ***
Closing old bugs.
