You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by kk...@apache.org on 2010/01/14 09:13:48 UTC
svn commit: r899098 - /tomcat/tc6.0.x/trunk/STATUS.txt
Author: kkolinko
Date: Thu Jan 14 08:13:48 2010
New Revision: 899098
URL: http://svn.apache.org/viewvc?rev=899098&view=rev
Log:
vote
Modified:
tomcat/tc6.0.x/trunk/STATUS.txt
Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=899098&r1=899097&r2=899098&view=diff
==============================================================================
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Jan 14 08:13:48 2010
@@ -127,7 +127,7 @@
http://svn.apache.org/viewvc?rev=712053&view=rev
Complete patch applicable to TC6:
http://people.apache.org/~rjung/patches/tc6-version_filter.patch
- +1: rjung, yoavs
+ +1: rjung, yoavs, kkolinko (with exception of text files)
-1:
kkolinko: (
-0 for changes of the *.txt files:
@@ -174,8 +174,13 @@
I haven't figured out why, but this also prevents buffered log messages being
lost on stop when running as a service.
http://svn.apache.org/viewvc?rev=898468&view=rev
- +1: markt, yoavs
+ +1: markt, yoavs, kkolinko
-1:
+ kkolinko: OK, understood. This patch is needed because you cannot
+ overwrite LogManager.reset() to clean all loggers, because in most cases
+ reset() is called without intention to clean everything: either
+ called explicitly, or from ClassLoaderLogManager.readConfiguration().
+
* Cleanup and well define log buffering behavior
http://svn.apache.org/viewvc?rev=898836&view=rev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org