This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via ca7ec46c41a2d026fc3e2ad137962cf1e679a16b (commit) from 13500debebed9bb352c9216ab295ec21a8cbe59a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=ca7ec46c41a2d026fc3e2ad13... http://github.com/ceki/logback/commit/ca7ec46c41a2d026fc3e2ad137962cf1e679a1... commit ca7ec46c41a2d026fc3e2ad137962cf1e679a16b Author: Ceki Gulcu <ceki@qos.ch> Date: Mon Oct 18 23:19:01 2010 +0200 editing diff --git a/logback-site/src/site/pages/manual/mdc.html b/logback-site/src/site/pages/manual/mdc.html index 9e24ced..afdb15b 100644 --- a/logback-site/src/site/pages/manual/mdc.html +++ b/logback-site/src/site/pages/manual/mdc.html @@ -36,11 +36,11 @@ complex distributed applications. Most real-world distributed systems need to deal with multiple clients simultaneously. In a typical multithreaded implementation of such a system, different - threads will handle different clients. A possible but discouraged - approach to differentiate the logging output of one client from - another consists of instantiating a new and separate logger for - each client. This technique promotes the proliferation of loggers - and considerably increases their management overhead. + threads will handle different clients. A possible but slightly + discouraged approach to differentiate the logging output of one + client from another consists of instantiating a new and separate + logger for each client. This technique promotes the proliferation + of loggers and may increase their management overhead. </p> <script src="../templates/setup.js" type="text/javascript"></script> @@ -94,6 +94,9 @@ public class MDC { information in each log entry. </p> + <p>Please note that MDC as implemented by logback-classic assumes + that values are placed into the MDC with moderate frequency. </p> + <p> The next application named <code><a href="../xref/chapters/mdc/SimpleMDC.html">SimpleMDC</a></code> diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 32f4256..537d28b 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -32,11 +32,20 @@ <h3>xxxx, 2010 - Release of version 0.9.26</h3> + <p>Fixed <a + href="http://jira.qos.ch/browse/LBCLASSIC-183">LBCLASSIC-183</a> + as reported by Anthony Whitford. Upon application restart, Tomcat + should no longer complain about ThreadLocal variables created + internally by logback. + </p> + <p>When stopped, <code>RollingFileAppender</code> now calls <code>stop()</code> on its policy objects, fixing <a href="http://jira.qos.ch/browse/LBCORE-114">LBCORE-114</a> reported by Anders Wallgren.</p> + + <h3>October 13th, 2010 - Release of version 0.9.25</h3> <p>Logback-classic now supports <a ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/mdc.html | 13 ++++++++----- logback-site/src/site/pages/news.html | 9 +++++++++ 2 files changed, 17 insertions(+), 5 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.