- logback-dev - mailman3.qos.ch

svn commit: r1280 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 24 Jan '07

24 Jan '07

Author: seb Date: Wed Jan 24 19:01:40 2007 New Revision: 1280 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Log: corrected figures Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Wed Jan 24 19:01:40 2007 @@ -1160,7 +1160,7 @@ When logging is turned off entirely, the cost of a log request consists of a method invocation plus an integer comparison. On a 3.2Ghz Pentium D machine this cost is typically -in the 500 - 600 nanosecond range. +around 20 nanoseconds. </p> <p> @@ -1204,22 +1204,17 @@ <h4>2. The performance of deciding whether to log or not to log when logging is turned on.</h4> <p> -This is essentially the performance of walking the logger hierarchy. -When logging is turned on, logback still needs to compare the level of the -log request with the level of the request logger. However, loggers may not have an -assigned level; they can inherit them from the logger hierarchy. Thus, before -inheriting a level, the logger may need to search its ancestors. +In logback, there is no need to walk the whole logger hierarchy. A logger knows +its effective level (that is, its level, once level inheritance has been +taken into consideration) when it is created. Should the level of a parent logger +be changed, then all child loggers will be contacted and handle the change. Thus, before +accepting or denying a request based on the effective level, the logger does not need +to search its ancestors. </p> <p> -There has been a serious effort to make this hierarchy walk to be as fast as -possible. For example, child loggers link only to their existing ancestors. -This significantly improves the speed of the walk, especially in <em>sparse</em> hierarchies. -</p> - -<p> -The cost of walking the hierarchy is typically 2 times slower than just -checking whether logging is turned off entirely. +Given this situation, it takes the same time to decide whether to log or not when logging +is turned on as it takes when logging is turned off. </p> <h4>3. Actual logging (formatting and writing to the output device)</h4> @@ -1229,7 +1224,7 @@ target destination. Here again, a serious effort was made to make layouts (formatters) perform as quickly as possible. The same is true for appenders. The typical cost of actually logging is -about 10 to 15 microseconds when logging to a file on the local machine. +about 9 to 12 microseconds when logging to a file on the local machine. It goes up to 1 millisecond when logging to a database on a remote server. </p>

1 0

svn commit: r1279 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 24 Jan '07

24 Jan '07

Author: seb Date: Wed Jan 24 16:08:27 2007 New Revision: 1279 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml Log: Added a performance section to chapter 2 Added direct <a name="" /> links in chapter 1 and 2 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Wed Jan 24 16:08:27 2007 @@ -85,7 +85,8 @@ are part of the core module. For the sake of genericity, logback-core has no notion of loggers. </p> - + + <a name="LoggerContext" /> <h3>Logger context</h3> <p>The first and foremost advantage of any logging API over plain @@ -353,6 +354,7 @@ parent <code>X</code>, which has an assigned level. </p> + <a name="PrintintMethods" /> <h3>Printing methods</h3> <p>By definition, the printing method determines the level of a @@ -455,6 +457,7 @@ // This request is disabled, because <span class="green bold">DEBUG</span> < <span class="blue">INFO</span>. barlogger.<span class="green bold">debug</span>("Exiting gas station search");</pre></div> + <a name="RetrievingLoggers" /> <h3>Retrieving Loggers</h3> <p> Calling the <code><a href="../apidocs/org/slf4j/LoggerFactory.html#getLogger(java.lang.String)">LoggerFactory.getLogger</a></code> @@ -505,6 +508,7 @@ located seems to be the best general strategy known so far. </p> + <a name="AppendersAndLayouts" /> <h3>Appenders and Layouts</h3> <p> @@ -662,6 +666,7 @@ the message of the request. </p> + <a name="ParametrizedLogging" /> <h3>Parameterized logging</h3> <p> @@ -759,6 +764,7 @@ <div class="source"><pre>Object[] paramArray = {newVal, below, above}; logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre></div> + <a name="Configuration" /> <h3>Configuration</h3> <p>Inserting log requests into the application code requires a @@ -1044,7 +1050,7 @@ the introduction. The output was generated due to this feature. </p> - +<a name="UnderTheHood" /> <h3>A peak under the hood</h3> <p> @@ -1134,5 +1140,104 @@ <a href="underTheHood.html"><img src="images/chapter2/underTheHoodSequence2_small.gif" /></a> +<a name="Performance" /> +<h3>Performance</h3> + +<p> +One of the often-cited arguments against logging is its computational cost. +This is a legitimate concern as even moderately sized applications can generate +thousands of log requests. Much effort is spent measuring and tweaking +logging performance. +Independently of these efforts, the user should still be aware of the following +performance issues. +</p> + +<h4>1. Logging performance when logging is turned off entirely</h4> + +<p> +You can turn off logging entirely by setting the level of the root logger +to <code>Level.OFF</code>, the highest possible level. +When logging is turned off entirely, +the cost of a log request consists of a method invocation plus an +integer comparison. On a 3.2Ghz Pentium D machine this cost is typically +in the 500 - 600 nanosecond range. +</p> + +<p> +However, any method invocation involves the "hidden" cost of parameter construction. +For example, for some logger <em>x</em> writing, +</p> + +<div class="source"><pre>x.debug("Entry number: " + i + "is " + entry[i]);</pre></div> + +<p> +incurs the cost of constructing the message parameter, i.e. converting both +integer <code>i</code> and <code>entry[i]</code> to a string, and concatenating +intermediate strings, regardless of whether the message will be logged or not. +</p> + +<p> +The cost of parameter construction can be quite high and depends on the size +of the parameters involved. To avoid the cost of parameter construction +you can use logback's parametrized logging: +</p> + +<div class="source"><pre>x.debug("Entry number: {} is {}", i, entry[i]);</pre></div> + +<p> +This will not incur the cost of parameter construction. Compared to the +previous call to the <code>debug()</code> method, this call will be faster by +a very wide margin. +The message will be formatted only if the request is processed to the appenders. +If it is processed, the component that formats the message offers high performance +and does not impact negatively the overall process. +It respectively takes 2 and 4 microseconds to format a message with 1 and 3 parameters. +</p> + +<p> +Please notice that, despite the performance points that we just discussed, inserting +logging statements in tight-loops or very frequently invoked code is a lose-lose proposal +and will not result in high performance. They will slow down your application even +if logging is turned off or generate massive (and hence useless) output if enabled. +</p> + +<h4>2. The performance of deciding whether to log or not to log when logging is turned on.</h4> + +<p> +This is essentially the performance of walking the logger hierarchy. +When logging is turned on, logback still needs to compare the level of the +log request with the level of the request logger. However, loggers may not have an +assigned level; they can inherit them from the logger hierarchy. Thus, before +inheriting a level, the logger may need to search its ancestors. +</p> + +<p> +There has been a serious effort to make this hierarchy walk to be as fast as +possible. For example, child loggers link only to their existing ancestors. +This significantly improves the speed of the walk, especially in <em>sparse</em> hierarchies. +</p> + +<p> +The cost of walking the hierarchy is typically 2 times slower than just +checking whether logging is turned off entirely. +</p> + +<h4>3. Actual logging (formatting and writing to the output device)</h4> + +<p> +This is the cost of formatting the log output and sending it to its +target destination. Here again, a serious effort was made to make +layouts (formatters) perform as quickly as possible. +The same is true for appenders. The typical cost of actually logging is +about 10 to 15 microseconds when logging to a file on the local machine. +It goes up to 1 millisecond when logging to a database on a remote server. +</p> + +<p> +Although feature-rich, one of the foremost design goals of logback was speed +of execution, a requirement which is second only to reliability. Some logback +components have been rewritten many times to improve performance. +</p> + </body> </document> Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml Wed Jan 24 16:08:27 2007 @@ -77,6 +77,7 @@ </p> </div> + <a name="Requirements" /> <h3>Requirements</h3> <p>Logback-classic module requires the presence @@ -213,21 +214,22 @@ <ol> - <li>Configure the logback environment. You can do so in several - more or less sophisticated ways. More on this later.</li> + <p>Configure the logback environment. You can do so in several + more or less sophisticated ways. More on this later.</p> - <li>In every class where you wish to perform logging, retrieve a + <p>In every class where you wish to perform logging, retrieve a <code>Logger</code> instance by invoking the <code>org.slf4j.LoggerFactory</code> class' <code>getLogger()</code> method, passing the current class name - or the class itself as parameter.</li> + or the class itself as parameter.</p> - <li>Use this logger instance by invoking its printing methods, + <p>Use this logger instance by invoking its printing methods, namely the debug(), info(), warn() and error(). This will - produce logging output on the configured appenders.</li> + produce logging output on the configured appenders.</p> </ol> - <h2>Building logback</h2> + <a name="BuildingLogback" /> + <h3>Building logback</h3> <p> Like many java applications today, logback relies on <a href="http://maven.apache.org">

1 0

svn commit: r1278 - in logback/trunk: log4j-bridge logback-site/src/site/resources/manual logback-site/src/site/resources/manual/images/chapter2 logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 24 Jan '07

24 Jan '07

Author: seb Date: Wed Jan 24 15:08:09 2007 New Revision: 1278 Added: logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence2.gif (contents, props changed) logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence2_small.gif (contents, props changed) Removed: logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence.gif Modified: logback/trunk/log4j-bridge/ (props changed) logback/trunk/logback-site/src/site/resources/manual/underTheHood.html logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Log: Modified sequence diagram Added: logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence2.gif ============================================================================== Binary file. No diff available. Added: logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence2_small.gif ============================================================================== Binary file. No diff available. Modified: logback/trunk/logback-site/src/site/resources/manual/underTheHood.html ============================================================================== --- logback/trunk/logback-site/src/site/resources/manual/underTheHood.html (original) +++ logback/trunk/logback-site/src/site/resources/manual/underTheHood.html Wed Jan 24 15:08:09 2007 @@ -3,7 +3,7 @@ <body> <h2>Under The Hood Sequence Diagram</h2> -<img src="images/chapter2/underTheHoodSequence.gif" /> +<img src="images/chapter2/underTheHoodSequence2.gif" /> </body> </html> Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Wed Jan 24 15:08:09 2007 @@ -1132,7 +1132,7 @@ want to click on the image to display its bigger version. </p> -<a target="blank" href="underTheHood.html"><img width="50%" height="50%" src="images/chapter2/underTheHoodSequence.gif" /></a> +<a href="underTheHood.html"><img src="images/chapter2/underTheHoodSequence2_small.gif" /></a> </body> </document>

1 0

svn commit: r1277 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 24 Jan '07

24 Jan '07

Author: seb Date: Wed Jan 24 11:35:14 2007 New Revision: 1277 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml logback/trunk/logback-site/src/site/xdocTemplates/manual/index.xml Log: minor modifs Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Wed Jan 24 11:35:14 2007 @@ -468,7 +468,7 @@ </tr> <tr> <td><b><span class="option">File</span></b></td> - <td><code>int</code></td> + <td><code>String</code></td> <td> The name of the file to write to. If the file does not exist, it is created. <br /> On the MS Windows platform users frequently forget to escape back slashes. Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/index.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/index.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/index.xml Wed Jan 24 11:35:14 2007 @@ -64,7 +64,7 @@ <a href="introduction.html"><b>Chapter 1: Introduction to logback</b></a> </p></li> <li><p> - <a href="joran.html"><b>Chapter 2: Architecture</b></a> + <a href="architecture.html"><b>Chapter 2: Architecture</b></a> </p></li> <li><p> <a href="joran.html"><b>Chapter 3: Logback configuration with Joran</b></a>

1 0

svn commit: r1276 - in logback/trunk/logback-site/src/site: resources/manual resources/manual/images/chapter2 xdocTemplates/manual
by noreply.seb＠qos.ch 23 Jan '07

23 Jan '07

Author: seb Date: Tue Jan 23 20:13:34 2007 New Revision: 1276 Added: logback/trunk/logback-site/src/site/resources/manual/images/chapter2/ logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence.gif (contents, props changed) logback/trunk/logback-site/src/site/resources/manual/underTheHood.html Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Log: Added a sequence diagram to the "under the hood" section Added: logback/trunk/logback-site/src/site/resources/manual/images/chapter2/underTheHoodSequence.gif ============================================================================== Binary file. No diff available. Added: logback/trunk/logback-site/src/site/resources/manual/underTheHood.html ============================================================================== --- (empty file) +++ logback/trunk/logback-site/src/site/resources/manual/underTheHood.html Tue Jan 23 20:13:34 2007 @@ -0,0 +1,9 @@ +<html> + + <body> + <h2>Under The Hood Sequence Diagram</h2> + +<img src="images/chapter2/underTheHoodSequence.gif" /> + +</body> +</html> Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Tue Jan 23 20:13:34 2007 @@ -1127,6 +1127,12 @@ its destination by each appender. </p> - +<p> +Here is a sequence UML diagram to show how everything works. You might +want to click on the image to display its bigger version. +</p> + +<a target="blank" href="underTheHood.html"><img width="50%" height="50%" src="images/chapter2/underTheHoodSequence.gif" /></a> + </body> </document>

1 0

svn commit: r1275 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 23 Jan '07

23 Jan '07

Author: seb Date: Tue Jan 23 17:39:15 2007 New Revision: 1275 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Log: added a "peak under the hood" section at the end of the document Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/architecture.xml Tue Jan 23 17:39:15 2007 @@ -1041,7 +1041,92 @@ <p> The last step of logback's configuration policy permits the use of a minimal logging configuration right out of the box. Remember the very first example of - this short introduction. The output was generated due to this feature. + the introduction. The output was generated due to this feature. </p> - </body> + + +<h3>A peak under the hood</h3> + +<p> +After we have introduced the essential logback components, we are now +ready to describe the steps that the logback framework takes when the user invokes +a logger's printing method. Let us now analyze the steps logback takes when the +user invokes the <code>info()</code> method of a +logger named <em>com.wombat</em>. +</p> + +<h4>1. Get the filter chain decision</h4> + +<p> +Logback's <code>TurboFilter</code> chain is called. These filters may +be used to prodvide a context-wide threshold, or to filter out certain +events based on basic logging informations such as <code>Marker</code>, +<code>Level</code>, <code>Logger</code>, message, or the <code>Throwable</code> +that was provided in the logging request. +If the reply of the filter chain is <code>FilterReply.DENY</code>, then the +logging request is dropped. If it is <code>FilterReply.NEUTRAL</code>, then +the next step is processed. In case the reply is <code>FilterReply.ACCEPT</code>, +the next step is skipped and the logging request is directly processed to step 3. +</p> + +<h4>2. Apply the Logger level filter</h4> + +<p> +Logback compares the effective level of the <em>com.wombat</em> logger +with the level of the request (in this example: <em>INFO</em>). If the logging +request is disabled, then logback will drop the request without further processing. +</p> + +<h4>3. Create a <code>LoggingEvent</code> object</h4> + +<p> +If the request passed the previous filter, or if the <code>TurboFilter</code> chain +gave a <code>FilterReply.ACCEPT</code> result, logback will create a +<code>ch.qos.logback.classic.LoggingEvent</code> object containing all the +relevant parameters of the request such as the logger of the request, the request +level, the message, the exception that might have been passed along the request, +the current time, the current thread, several information about the class that +issued the logging request and the <code>MDC</code> map. Note that some of these fields +are initialized lazily, that is only when they are actually needed. +</p> + +<h4>4. Invoking appenders</h4> + +<p> +After the creation of a <code>LoggingEvent</code> object, logback will proceed +to invoke the <code>doAppend()</code> methods of all the applicable appenders, +that is, the appenders inherited from the logger context. +</p> +<p> +All appenders shipped with the logback distribution extend the +<code>AppenderBase</code> abstract class that implements the +<code>doAppend</code> method in a synchronized block ensuring thread-safety. +The <code>doAppend()</code> method of <code>AppenderBase</code> also invokes +custom filters attached to the appender, if any such filters exist. +Custom filters, which can be dynamically attached to any appender, +are presented Chapter 6. +</p> + +<h4>5. Formatting the <code>LoggingEvent</code></h4> + +<p> +It is responsibility of the invoked appender to format the +logging event. However, most (but not all) appenders delegate +the task of formatting the logging event to their layout. Their +layout formats the <code>LoggingEvent</code> instance and returns the +result as a String. Note that some appenders, such as the +<code>SocketAppender</code>, do not transform the logging event +into a string but serialize it instead. +Consequently, they do not require nor have a layout. +</p> + +<h4>6. Sending out the <code>LoggingEvent</code></h4> + +<p> +After the logging event is fully formatted it is sent to +its destination by each appender. +</p> + + +</body> </document>

1 0

svn commit: r1274 - in logback/trunk: . log4j-bridge logback-access logback-classic logback-core logback-examples logback-site logback-site/src/site logback-skin src/site
by noreply.seb＠qos.ch 23 Jan '07

23 Jan '07

Author: seb Date: Tue Jan 23 15:43:11 2007 New Revision: 1274 Modified: logback/trunk/log4j-bridge/pom.xml logback/trunk/logback-access/pom.xml logback/trunk/logback-classic/pom.xml logback/trunk/logback-core/pom.xml logback/trunk/logback-examples/pom.xml logback/trunk/logback-site/pom.xml logback/trunk/logback-site/src/site/site.xml logback/trunk/logback-skin/pom.xml logback/trunk/pom.xml logback/trunk/src/site/site.xml Log: version of logback updated to 0.9-SNAPSHOT Modified: logback/trunk/log4j-bridge/pom.xml ============================================================================== --- logback/trunk/log4j-bridge/pom.xml (original) +++ logback/trunk/log4j-bridge/pom.xml Tue Jan 23 15:43:11 2007 @@ -5,14 +5,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>log4j-bridge</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <packaging>jar</packaging> <name>Log4j Bridge Module</name> Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Tue Jan 23 15:43:11 2007 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-access</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <packaging>jar</packaging> <name>Logback Access Module</name> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Tue Jan 23 15:43:11 2007 @@ -5,14 +5,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <packaging>jar</packaging> <name>Logback Classic Module</name> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Tue Jan 23 15:43:11 2007 @@ -5,14 +5,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <packaging>jar</packaging> <name>Logback Core Module</name> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Tue Jan 23 15:43:11 2007 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-examples</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <packaging>jar</packaging> <name>Logback Examples Module</name> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Tue Jan 23 15:43:11 2007 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> @@ -11,7 +11,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-site</artifactId> <packaging>jar</packaging> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <name>Logback Site</name> <url>http://logback.qos.ch</url> Modified: logback/trunk/logback-site/src/site/site.xml ============================================================================== --- logback/trunk/logback-site/src/site/site.xml (original) +++ logback/trunk/logback-site/src/site/site.xml Tue Jan 23 15:43:11 2007 @@ -4,7 +4,7 @@ <skin> <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </skin> <publishDate position="navigation-bottom" format="dd-MM-yyyy"/> Modified: logback/trunk/logback-skin/pom.xml ============================================================================== --- logback/trunk/logback-skin/pom.xml (original) +++ logback/trunk/logback-skin/pom.xml Tue Jan 23 15:43:11 2007 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </parent> @@ -12,7 +12,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> <packaging>jar</packaging> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <name>Logback Skin</name> <url>http://logback.qos.ch</url> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Tue Jan 23 15:43:11 2007 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> <packaging>pom</packaging> <name>Logback-Parent</name> Modified: logback/trunk/src/site/site.xml ============================================================================== --- logback/trunk/src/site/site.xml (original) +++ logback/trunk/src/site/site.xml Tue Jan 23 15:43:11 2007 @@ -4,7 +4,7 @@ <skin> <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> - <version>0.8.1</version> + <version>0.9-SNAPSHOT</version> </skin> <!-- <publishDate position="navigation-bottom" format="dd-MM-yyyy"/>

1 0

[ANN] Release of logback 0.7.1
by Sebastien Pennec 23 Jan '07

23 Jan '07

December 19th, 2006 - Release of version 0.7 Version 0.7.1 of logback has been released. This version contains more detailled information about logback access module, and its JMX components. A dedicated page[1] explains how to configure and use logback access in Tomcat and Jetty, and access some of its components via JMX. Links: [1] http://logback.qos.ch/access.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

1 1

svn commit: r1273 - logback/tags/release-0.8.1
by noreply.seb＠qos.ch 23 Jan '07

23 Jan '07

Author: seb Date: Tue Jan 23 15:27:07 2007 New Revision: 1273 Added: logback/tags/release-0.8.1/ - copied from r1272, /logback/trunk/ Log: Tagging release 0.8.1

1 0

svn commit: r1272 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 23 Jan '07

23 Jan '07

Author: seb Date: Tue Jan 23 15:24:23 2007 New Revision: 1272 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml Log: corrected links Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/introduction.xml Tue Jan 23 15:24:23 2007 @@ -87,7 +87,7 @@ <p>Let us now begin experimenting with logback.</p> -<em>Example 1.1: Basic template for logging (<a href="xref/chapter1/HelloWorld1.html">logback-examples/src/main/java/chapter1/HelloWorld1.java</a>)</em> +<em>Example 1.1: Basic template for logging (<a href="../xref/chapter1/HelloWorld1.html">logback-examples/src/main/java/chapter1/HelloWorld1.java</a>)</em> <div class="source"><pre>package chapter1; import org.slf4j.Logger; @@ -159,7 +159,7 @@ class. </p> -<em>Example 1.2: Printing Logger Status (<a href="xref/chapter1/HelloWorld2.html">logback-examples/src/main/java/chapter1/HelloWorld2.java</a>)</em> +<em>Example 1.2: Printing Logger Status (<a href="../xref/chapter1/HelloWorld2.html">logback-examples/src/main/java/chapter1/HelloWorld2.java</a>)</em> <div class="source"><pre>package chapter1; import org.slf4j.Logger;

1 0