On 22/01/2017 15:59, Violeta Georgieva wrote: > The proposed Apache Tomcat 6.0.50 release is now available for voting. > > Note: This is the last Tomcat 6 release. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.50/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1119/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_50/ > > The proposed 6.0.50 release is: > [ ] Broken - do not release > [X] Stable - go ahead and release as 6.0.50 Stable
I ran the TCKs with the following results. Servlet 2.5: I had to make the following changes from the default configuration - Enabled STRICT_SERVLET_COMPLIANCE - Disabled XML validation else Jasper's web.xml parsing fails which in turn triggers TCK failures. This appears to be mainly due to testing with Java 5. The problems look fixable (use same approach as Digester which does not fail) but I don't plan to fix this since this as a) this is probably the last 6.0.x release and b) I'm fairly sure this is a Java 5 issue - Disabled TLD validation else some TCK tests fail since enabling validation injects some init parameters into the ServletContext which trigger failures because the TCK is not expecting them - Enabled crossContext since the TCK tests that feature - The signature test fails but I have never been able to get it to pass for 2.5. I suspect a local configuration problem . A manual check of the API has previously confirmed it is correct and there have been no changes to the API for the spec classes. JSP 2.1 I had to make the following changes from the default configuration - Enabled STRICT_SERVLET_COMPLIANCE - Disbaled TLD validation since the TLDs that ship with the TCK fail validation - Disable development mode since it changes some exception types which in turn causes test failures. - One TCK test fails because an associated JSP no longer compiles because it reaches the 64k method limit. The JSP has a very large number of nested tags. I'm going to take another look at the JSP Generation to see if there is anything we can do to make even a small improvement. With the exception of the JSP method limit, I have seen all of the above previous 6.0.x releases. I do no consider the JSP method limit a show-stopper since you need a lot of tags on a page before it is an issue. Hence, I'm voting stable. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
