svn commit: r1215115 - /tomcat/trunk/test/org/apache/jasper/compiler/TestParser.java

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:11:31 2011 New Revision: 1215115 URL: http://svn.apache.org/viewvc?rev=1215115view=rev Log: Correct test Modified: tomcat/trunk/test/org/apache/jasper/compiler/TestParser.java Modified: tomcat/trunk/test/org/apache/jasper/compiler/TestParser.java URL:

svn commit: r1215118 - in /tomcat/trunk/test: org/apache/jasper/compiler/TestParser.java webapp-3.0/bug52335.jsp

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:12:23 2011 New Revision: 1215118 URL: http://svn.apache.org/viewvc?rev=1215118view=rev Log: Extend the test case Modified: tomcat/trunk/test/org/apache/jasper/compiler/TestParser.java tomcat/trunk/test/webapp-3.0/bug52335.jsp Modified:

svn commit: r1215119 - /tomcat/trunk/java/org/apache/jasper/compiler/Parser.java

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:13:00 2011 New Revision: 1215119 URL: http://svn.apache.org/viewvc?rev=1215119view=rev Log: Revert fix for https://issues.apache.org/bugzilla/show_bug.cgi?id=52335 Modified: tomcat/trunk/java/org/apache/jasper/compiler/Parser.java Modified:

svn commit: r1215121 - /tomcat/trunk/java/org/apache/jasper/compiler/Parser.java

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:13:36 2011 New Revision: 1215121 URL: http://svn.apache.org/viewvc?rev=1215121view=rev Log: Better fix for https://issues.apache.org/bugzilla/show_bug.cgi?id=52335 Modified: tomcat/trunk/java/org/apache/jasper/compiler/Parser.java Modified:

svn commit: r1215122 - in /tomcat/tc7.0.x/trunk: ./ java/org/apache/jasper/compiler/Parser.java test/org/apache/jasper/compiler/TestParser.java test/webapp-3.0/bug52335.jsp

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:14:50 2011 New Revision: 1215122 URL: http://svn.apache.org/viewvc?rev=1215122view=rev Log: Correct fix for https://issues.apache.org/bugzilla/show_bug.cgi?id=52335 Modified: tomcat/tc7.0.x/trunk/ (props changed)

svn commit: r1215124 - /tomcat/tc6.0.x/trunk/STATUS.txt

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:15:36 2011 New Revision: 1215124 URL: http://svn.apache.org/viewvc?rev=1215124view=rev Log: Update proposal Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL:

svn commit: r1215125 - /tomcat/tc5.5.x/trunk/STATUS.txt

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 13:15:59 2011 New Revision: 1215125 URL: http://svn.apache.org/viewvc?rev=1215125view=rev Log: Update proposal Modified: tomcat/tc5.5.x/trunk/STATUS.txt Modified: tomcat/tc5.5.x/trunk/STATUS.txt URL:

Re: svn commit: r1214855 - in /tomcat/trunk: java/org/apache/jasper/compiler/Parser.java test/org/apache/jasper/compiler/TestParser.java test/webapp-3.0/bug52335.jsp

2011-12-16 Thread Mark Thomas
On 15/12/2011 23:22, ma...@apache.org wrote: Konstantin Kolinko knst.koli...@gmail.com wrote: 1. The test fix is wrong. \% should print % 2. Note // Output the first character comment in parseTemplateText(). That is special handling of the first character. My understanding of the

[jira] [Created] (MTOMCAT-109) protocolorg.apache.coyote.http11.Http11NioProtocol/protocol not honoured

2011-12-16 Thread Morten Haraldsen (Created) (JIRA)
protocolorg.apache.coyote.http11.Http11NioProtocol/protocol not honoured Key: MTOMCAT-109 URL: https://issues.apache.org/jira/browse/MTOMCAT-109 Project: Apache Tomcat Maven

[jira] [Commented] (MTOMCAT-109) protocolorg.apache.coyote.http11.Http11NioProtocol/protocol not honoured

2011-12-16 Thread Morten Haraldsen (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13170976#comment-13170976 ] Morten Haraldsen commented on MTOMCAT-109: -- This is effectively blocking usage

[jira] [Updated] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

2011-12-16 Thread Brad Giaccio (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Giaccio updated MTOMCAT-108: - Attachment: https.patch I've tested this patch on Mac OSX 10.6.8, Fedora Core 16, and Redhat

[jira] [Updated] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

2011-12-16 Thread Olivier Lamy (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-108: - Fix Version/s: 2.0 THe httpsPort flag starts another http thread not an https thread

[jira] [Updated] (MTOMCAT-109) protocolorg.apache.coyote.http11.Http11NioProtocol/protocol not honoured

2011-12-16 Thread Olivier Lamy (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-109: - Affects Version/s: 2.0 Fix Version/s: 2.0 Assignee: Olivier Lamy need a

[jira] [Commented] (MTOMCAT-109) protocolorg.apache.coyote.http11.Http11NioProtocol/protocol not honoured

2011-12-16 Thread Olivier Lamy (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13170995#comment-13170995 ] Olivier Lamy commented on MTOMCAT-109: -- do you prefer something configurable tru cli

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

2011-12-16 Thread Olivier Lamy (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13170996#comment-13170996 ] Olivier Lamy commented on MTOMCAT-108: -- @Brad looks a good patch. Note the maven

svn commit: r1215161 - /tomcat/tc6.0.x/trunk/STATUS.txt

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 14:50:23 2011 New Revision: 1215161 URL: http://svn.apache.org/viewvc?rev=1215161view=rev Log: Vote Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL:

svn commit: r1215162 - /tomcat/tc6.0.x/trunk/STATUS.txt

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 14:51:58 2011 New Revision: 1215162 URL: http://svn.apache.org/viewvc?rev=1215162view=rev Log: Vote Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL:

svn commit: r1215167 - in /tomcat/tc6.0.x/trunk: res/maven/mvn-pub.xml webapps/docs/changelog.xml

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 14:55:15 2011 New Revision: 1215167 URL: http://svn.apache.org/viewvc?rev=1215167view=rev Log: Fix the publishing side of https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 Modified: tomcat/tc6.0.x/trunk/res/maven/mvn-pub.xml

Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Mark Thomas
It appears that Maven artefact publishing has been moved from people.a.o (that all the release scripts are written to use) to using Nexus. See [1] I have a number of issues with this: 1. There was zero discussion of this on the dev list. 2. Maven publishing for snapshots, release candidates and

DO NOT REPLY [Bug 52124] Tomcat Maven metadata only includes the latest release

2011-12-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 --- Comment #3 from Mark Thomas ma...@apache.org 2011-12-16 15:23:33 UTC --- Patch applied. Leaving this open as the historical metadata needs to be fixed. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email

svn commit: r1215179 - /tomcat/tc6.0.x/trunk/STATUS.txt

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 15:24:16 2011 New Revision: 1215179 URL: http://svn.apache.org/viewvc?rev=1215179view=rev Log: Remove applied patch Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL:

svn commit: r1215181 - /tomcat/tc6.0.x/trunk/STATUS.txt

2011-12-16 Thread markt
Author: markt Date: Fri Dec 16 15:25:02 2011 New Revision: 1215181 URL: http://svn.apache.org/viewvc?rev=1215181view=rev Log: Vote Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL:

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread jean-frederic clere
On 12/16/2011 04:20 PM, Mark Thomas wrote: It appears that Maven artefact publishing has been moved from people.a.o (that all the release scripts are written to use) to using Nexus. See [1] I have a number of issues with this: 1. There was zero discussion of this on the dev list. 2. Maven

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Mark Thomas
On 16/12/2011 15:43, jean-frederic clere wrote: On 12/16/2011 04:20 PM, Mark Thomas wrote: It appears that Maven artefact publishing has been moved from people.a.o (that all the release scripts are written to use) to using Nexus. See [1] I have a number of issues with this: 1. There was

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Antonio Petrelli
Please Mark calm down. Being possible to deploy to Nexus does not mean that the project is configured to do that. To enable this, you need to configure the needed POM metadata (SCM, website) and let the master POM of Tomcat be child of the Apache Master pom. Even if you have done this steps, if

DO NOT REPLY [Bug 52271] ArrayIndexOutOfBoundsException in CompositeELResolver.add

2011-12-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=52271 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Mark Thomas
On 16/12/2011 16:06, Antonio Petrelli wrote: Please Mark calm down. No, I will not calm down. The release process has been changed without prior discussion and on top of that it is now broken for Maven artefacts. That is not acceptable. Being possible to deploy to Nexus does not mean that the

[Tomcat Wiki] Update of LocalBadContent by ChuckCaldarale

2011-12-16 Thread Apache Wiki
Dear Wiki user, You have subscribed to a wiki page or wiki category on Tomcat Wiki for change notification. The LocalBadContent page has been changed by ChuckCaldarale: http://wiki.apache.org/tomcat/LocalBadContent?action=diffrev1=38rev2=39 Comment: spam prevention masterjin\.com

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Mark Thomas
On 16/12/2011 16:15, Mark Thomas wrote: On 16/12/2011 16:06, Antonio Petrelli wrote: Please Mark calm down. No, I will not calm down. The release process has been changed without prior discussion and on top of that it is now broken for Maven artefacts. That is not acceptable. Being

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread sebb
On 16 December 2011 16:15, Mark Thomas ma...@apache.org wrote: On 16/12/2011 16:06, Antonio Petrelli wrote: Please Mark calm down. No, I will not calm down. The release process has been changed without prior discussion and on top of that it is now broken for Maven artefacts. That is not

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Mark Thomas
On 16/12/2011 19:38, sebb wrote: On 16 December 2011 16:15, Mark Thomas ma...@apache.org wrote: On 16/12/2011 16:06, Antonio Petrelli wrote: Please Mark calm down. No, I will not calm down. The release process has been changed without prior discussion and on top of that it is now broken for

Publishing process for JARs for Maven Central

2011-12-16 Thread Mark Thomas
All, There are currently two options for publishing JARs to Maven Central: 1. scp+rsync via people.a.o 2. Nexus Personally, my only requirements are: a) that the JARs reach Maven Central b) publishing is as simple as running a single script I don't particularly care about the details. As long

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Antonio Petrelli
2011/12/16 Mark Thomas ma...@apache.org On 16/12/2011 16:06, Antonio Petrelli wrote: Please Mark calm down. No, I will not calm down. The release process has been changed without prior discussion and on top of that it is now broken for Maven artefacts. That is not acceptable. Mark,

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

2011-12-16 Thread Olivier Lamy (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13171218#comment-13171218 ] Olivier Lamy commented on MTOMCAT-108: -- btw regarding this obfuscate stuff I wonder

Re: Publishing process for JARs for Maven Central

2011-12-16 Thread Mladen Turk
On 12/16/2011 08:56 PM, Mark Thomas wrote: All, I know option 1 works ... Does anyone else have any requirements / views that would suggest one approach is better than the other? If it ain't broken don't fix it. Regards -- ^TM

Re: Move to Nexus with no community discussion. WTF?

2011-12-16 Thread Mark Thomas
On 16/12/2011 20:21, Antonio Petrelli wrote: 2011/12/16 Mark Thomas ma...@apache.org On 16/12/2011 16:06, Antonio Petrelli wrote: Please Mark calm down. No, I will not calm down. The release process has been changed without prior discussion and on top of that it is now broken for Maven

svn commit: r1215319 - in /tomcat/tc6.0.x/trunk: res/maven/mvn-pub.xml webapps/docs/changelog.xml

2011-12-16 Thread kkolinko
Author: kkolinko Date: Fri Dec 16 22:25:18 2011 New Revision: 1215319 URL: http://svn.apache.org/viewvc?rev=1215319view=rev Log: Followup to r1215167 Fix copy-pasted description Correct changelog entry a) It is in 6.0.36 b) Mention https://issues.apache.org/bugzilla/show_bug.cgi?id=49402 The juli

DO NOT REPLY [Bug 52124] Tomcat Maven metadata only includes the latest release

2011-12-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 --- Comment #4 from Konstantin Kolinko knst.koli...@gmail.com 2011-12-16 22:35:55 UTC --- The http://repo1.maven.org/maven2/org/apache/tomcat/catalina/maven-metadata.xml file mentioned in MVNCENTRAL-139 as of now lists 6.0.33 and 6.0.35

Re: Publishing process for JARs for Maven Central

2011-12-16 Thread Yoav Shapira
On Fri, Dec 16, 2011 at 2:56 PM, Mark Thomas ma...@apache.org wrote: All, There are currently two options for publishing JARs to Maven Central: 1. scp+rsync via people.a.o 2. Nexus I don't have a strong preference between them. Is there a difference between the two approaches in how fast

DO NOT REPLY [Bug 52124] Tomcat Maven metadata only includes the latest release

2011-12-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 --- Comment #5 from Sebb s...@apache.org 2011-12-17 00:19:45 UTC --- (In reply to comment #4) The http://repo1.maven.org/maven2/org/apache/tomcat/catalina/maven-metadata.xml file mentioned in MVNCENTRAL-139 as of now lists 6.0.33 and

Re: Publishing process for JARs for Maven Central

2011-12-16 Thread sebb
On 16 December 2011 23:45, Yoav Shapira yo...@apache.org wrote: On Fri, Dec 16, 2011 at 2:56 PM, Mark Thomas ma...@apache.org wrote: All, There are currently two options for publishing JARs to Maven Central: 1. scp+rsync via people.a.o 2. Nexus I don't have a strong preference between

[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) failed

2011-12-16 Thread Bill Barker
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration.

Re: Publishing process for JARs for Maven Central

2011-12-16 Thread Phil Steitz
On 12/16/11 12:56 PM, Mark Thomas wrote: All, There are currently two options for publishing JARs to Maven Central: 1. scp+rsync via people.a.o 2. Nexus Personally, my only requirements are: a) that the JARs reach Maven Central b) publishing is as simple as running a single script I