Re: [VOTE] Release Apache Tomcat 6.0.39

2014-01-30 Thread Keiichi Fujino
2014-01-28 Mark Thomas ma...@apache.org: The proposed Apache Tomcat 6.0.39 release candidate is now available for voting. The main changes since 6.0.37 are: - Updated to use the Eclipse compiler 4.3.1 - Back-ported various improvements to the validation of XML configuration files from

Re: [VOTE] Release Apache Tomcat 6.0.39

2014-01-29 Thread Ognjen Blagojevic
On 28.1.2014 0:08, Mark Thomas wrote: The proposed Apache Tomcat 6.0.39 release candidate is now available for voting. ... The proposed 6.0.39 release is: [ ] Broken - do not release [X] Stable - go ahead and release as 6.0.39 Stable Tested .zip distribution on Windows 7 64-bit: - Tested

Re: [VOTE] Release Apache Tomcat 6.0.39

2014-01-28 Thread Rainer Jung
On 28.01.2014 00:08, Mark Thomas wrote: The proposed Apache Tomcat 6.0.39 release candidate is now available for voting. The main changes since 6.0.37 are: - Updated to use the Eclipse compiler 4.3.1 - Back-ported various improvements to the validation of XML configuration files from

Re: [VOTE] Release Apache Tomcat 6.0.39

2014-01-28 Thread Konstantin Kolinko
2014-01-28 Mark Thomas ma...@apache.org: The proposed 6.0.39 release is: [ ] Broken - do not release [X] Stable - go ahead and release as 6.0.39 Stable Ack. Seeing these two issues with Java 5u20 (32-bit, Windows), to be specific. Issue 1 === XML validation with DTDs on Java 5 is

[VOTE] Release Apache Tomcat 6.0.39

2014-01-27 Thread Mark Thomas
The proposed Apache Tomcat 6.0.39 release candidate is now available for voting. The main changes since 6.0.37 are: - Updated to use the Eclipse compiler 4.3.1 - Back-ported various improvements to the validation of XML configuration files from Tomcat 7 - Avoid CVE-2013-1571 when generating

Re: [VOTE] Release Apache Tomcat 6.0.39

2014-01-27 Thread Mark Thomas
The proposed 6.0.39 release is: [ ] Broken - do not release [X] Stable - go ahead and release as 6.0.39 Stable Issue 1 === XML validation with DTDs on Java 5 is broken. Switching to Java 6 fixes this. Given the support status of Java 5 I don't plan on addressing this other than