svn commit: r572860 - /tomcat/container/tc5.5.x/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java

Author: markt Date: Tue Sep 4 19:15:35 2007 New Revision: 572860 URL: http://svn.apache.org/viewvc?rev=572860&view=rev Log: Port improved fix for 33774 that adds a check for the alternative exception to the remaining point where it could be seen. Modified: tomcat/container/tc5.5.x/catalina

svn commit: r572859 - /tomcat/tc6.0.x/trunk/java/org/apache/catalina/realm/JNDIRealm.java

Author: markt Date: Tue Sep 4 19:14:45 2007 New Revision: 572859 URL: http://svn.apache.org/viewvc?rev=572859&view=rev Log: Improve fix for 33774 by adding check for alternative exception to the remaining point where it could be seen. Modified: tomcat/tc6.0.x/trunk/java/org/apache/catalina/

DO NOT REPLY [Bug 33774] - JNDIRealm fails when server disconnects after time

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

svn commit: r572857 - /tomcat/jasper/tc5.5.x/.project

Author: markt Date: Tue Sep 4 19:04:35 2007 New Revision: 572857 URL: http://svn.apache.org/viewvc?rev=572857&view=rev Log: Remove duplicate line Modified: tomcat/jasper/tc5.5.x/.project Modified: tomcat/jasper/tc5.5.x/.project URL: http://svn.apache.org/viewvc/tomcat/jasper/tc5.5.x/.proje

DO NOT REPLY [Bug 30949] - After Failed Include, Request and Response not Unwrapped

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

svn commit: r572856 - in /tomcat/tc6.0.x/trunk: java/org/apache/catalina/core/ApplicationDispatcher.java webapps/docs/changelog.xml

Author: markt Date: Tue Sep 4 19:01:02 2007 New Revision: 572856 URL: http://svn.apache.org/viewvc?rev=572856&view=rev Log: Port improved fix for bug 30949 to TC6. Modified: tomcat/tc6.0.x/trunk/java/org/apache/catalina/core/ApplicationDispatcher.java tomcat/tc6.0.x/trunk/webapps/docs/c

svn commit: r572855 - /tomcat/container/tc5.5.x/webapps/docs/changelog.xml

Author: markt Date: Tue Sep 4 18:59:22 2007 New Revision: 572855 URL: http://svn.apache.org/viewvc?rev=572855&view=rev Log: Fix the changelog I broke on previous commit Modified: tomcat/container/tc5.5.x/webapps/docs/changelog.xml Modified: tomcat/container/tc5.5.x/webapps/docs/changelog.xm

svn commit: r572854 - in /tomcat/container/tc5.5.x: catalina/src/share/org/apache/catalina/core/ApplicationDispatcher.java webapps/docs/changelog.xml

Author: markt Date: Tue Sep 4 18:53:49 2007 New Revision: 572854 URL: http://svn.apache.org/viewvc?rev=572854&view=rev Log: An alternative fix for 30949 that does not require additional try/catch/finally blocks Also remove unnecessary unwrapping now that unwrapRequest() and unwrapResponse() are

Re: [VOTE] Make released versions RTC

Remy Maucherat wrote: Jim Jagielski wrote: I'm +1 for this type of procedure, but I don't see how this can be shoehorned into the current setup and layout of TC. The basic ideas behind httpd and apr are: o There is a set development location (currently trunk) which operates under CTR.

Re: [VOTE] Make released versions RTC

Jim Jagielski wrote: I'm +1 for this type of procedure, but I don't see how this can be shoehorned into the current setup and layout of TC. The basic ideas behind httpd and apr are: o There is a set development location (currently trunk) which operates under CTR. o There is a set relea

Re: [VOTE] Make released versions RTC

Filip Hanik - Dev Lists wrote: -1, that means the entire tomcat project is RTC, since you just voted to get rid of trunk Personally, using the CTR model, I noticed a number of people always considered the "R" portion invalid, and useless chatter that is best ignored. My take on the situation

Re: [VOTE] Make released versions RTC

On Sep 4, 2007, at 4:53 AM, jean-frederic clere wrote: Hi, I would also propose that we take an handling of release branches similar to httpd. The release branches are: /tomcat/tc6.0.x/trunk /tomcat/build/tc5.5.x/ /tomcat/container/tc5.5.x /tomcat/jasper/tc5.5.x/ (Note it uses /tomcat/connec

Re: [VOTE] Make released versions RTC

-1, that means the entire tomcat project is RTC, since you just voted to get rid of trunk Filip jean-frederic clere wrote: Hi, I would also propose that we take an handling of release branches similar to httpd. The release branches are: /tomcat/tc6.0.x/trunk /tomcat/build/tc5.5.x/ /tomcat/

Re: [VOTE] Make released versions RTC

In that case > [ ] +1 > [ ] 0 > [X] -1 > For ensuring new features start in "trunk" and work their way back, I'd +1. But since bugs (in BZ not marked as enhancement) would also need RTC - that is my reason for -1. -Tim jean-frederic clere wrote: Tim Funk wrote: What is a change? Any com

DO NOT REPLY [Bug 43303] New: - Versioning under Windows not reported by many connector components

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [VOTE] Make released versions RTC

Tim Funk wrote: > What is a change? Any commit? > > Is a change only for new features and bug fixes are out of scope? My idea is to have it for all commits but only on release branches. The idea is more to force people participating on the development of new feature and help to fixing bugs. Chee

Re: [VOTE] Make released versions RTC

jean-frederic clere wrote: > The votes will get in a file named STATUS file and once accepted in a > file named CHANGES. > The proposal of backports/fixes should be a description of the > feature/PR number and a link to a commit (in another branch or sandbox) > or a patch (diff -u) against the bran

Re: [VOTE] Make released versions RTC

jean-frederic clere wrote: Hi, I would also propose that we take an handling of release branches similar to httpd. The release branches are: /tomcat/tc6.0.x/trunk /tomcat/build/tc5.5.x/ /tomcat/container/tc5.5.x /tomcat/jasper/tc5.5.x/ (Note it uses /tomcat/connectors/trunk) /tomcat/build/bra

Re: [VOTE] Make released versions RTC

What is a change? Any commit? Is a change only for new features and bug fixes are out of scope? -Tim jean-frederic clere wrote: Hi, I would also propose that we take an handling of release branches similar to httpd. The votes will get in a file named STATUS file and once accepted in a file n

Re: [VOTE] Make released versions RTC

Hey, On 9/4/07, jean-frederic clere <[EMAIL PROTECTED]> wrote: > I would also propose that we take an handling of release branches > similar to httpd. > The votes will get in a file named STATUS file and once accepted in a > file named CHANGES. > The proposal of backports/fixes should be a descri

Re: [VOTE] Move trunk to sandbox

Remy Maucherat wrote: [X] +1 [ ] 0 [ ] -1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Make released versions RTC

Hi, I would also propose that we take an handling of release branches similar to httpd. The release branches are: /tomcat/tc6.0.x/trunk /tomcat/build/tc5.5.x/ /tomcat/container/tc5.5.x /tomcat/jasper/tc5.5.x/ (Note it uses /tomcat/connectors/trunk) /tomcat/build/branches/tc5.0.x /tomcat/contain