DO NOT REPLY [Bug 41830] - session replication stop,when use container managed security and cluster.session replication stop,when use container managed security and cluster.

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: svn commit: r575332 - in /tomcat/tc6.0.x/trunk: java/org/apache/naming/resources/FileDirContext.java webapps/docs/changelog.xml

Filip Hanik - Dev Lists wrote: > Mladen Turk wrote: >> Filip Hanik - Dev Lists wrote: >>> Mladen Turk wrote: This simply has to stop. >>> >>> taking trunk away, this turn of events is expected. I wish everyone >>> would have thought of that before we got caught up in the personal, >>> and

DO NOT REPLY [Bug 34868] - allow to register a trust store for a session that becomes effective before CLIENT-CERT auth is executed on requests

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: r576971 - in /tomcat/connectors/trunk/jk/native: apache-1.3/mod_jk.c apache-2.0/mod_jk.c

Author: jim Date: Tue Sep 18 09:24:09 2007 New Revision: 576971 URL: http://svn.apache.org/viewvc?rev=576971&view=rev Log: Useful to log the shared memory segment size. Since JkShmSize takes an int and uses that throughout, this is a pretty safe cast unless, of course, people abuse JkShmSize, but

Review model take 2

Hi, Another more precise draft. Patches which would go to review would be: - API changing patches (any protected or above signature change) on APIs which are accessible to the user either from confirguration or programmatically - any other commit for which a committer asks for the RTC procedur

Re: Review model take 2

Hey, On 9/18/07, Remy Maucherat <[EMAIL PROTECTED]> wrote: > Another more precise draft. > than discussions about the validity of the disagreement). It would > introduce a small delay for committing certain patches and a minor > slowdown for development pace in theory, but in practice I've notice

Re: Review model take 2

+1 I think one exception ( or maybe something that should be easily fast-tracked ): - adding new hooks to allow such features to be developed and plugged in as separate modules For any new feature or bigger change to a component that already has a plugin mechanism ( connector, etc ) - it would be

DO NOT REPLY [Bug 43423] New: - catalina.sh -force too fast

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

DO NOT REPLY [Bug 43423] - catalina.sh -force too fast

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

DO NOT REPLY [Bug 43424] New: - MD5 files for 6.0.14 contain unexpanded "${md5sum.binary-prefix}"

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: Review model take 2

+1 -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Review model take 2

Remy Maucherat wrote: Hi, Another more precise draft. Patches which would go to review would be: - API changing patches (any protected or above signature change) on APIs which are accessible to the user either from confirguration or programmatically yes, makes sense - any other commit for wh

DO NOT REPLY [Bug 43425] New: - Non-compliant annotations

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

DO NOT REPLY [Bug 43425] - Non-compliant annotations

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: Review model take 2

+1 Cheers Jean-Frederic Remy Maucherat wrote: > Hi, > > Another more precise draft. > > Patches which would go to review would be: > - API changing patches (any protected or above signature change) on APIs > which are accessible to the user either from confirguration or > programmatically > -

Re: Review model take 2

Filip Hanik - Dev Lists wrote: > Remy Maucherat wrote: >> Hi, >> >> Another more precise draft. >> >> Patches which would go to review would be: >> - API changing patches (any protected or above signature change) on >> APIs which are accessible to the user either from confirguration or >> programma