- logback-dev - mailman3.qos.ch

Release of logback version 0.9.13
by Ceki Gulcu 05 Dec '08

05 Dec '08

5th of December 2008 - Release of version 0.9.13 Version 0.9.13 is a maintenance release fixing LBCLASSIC-91, a severe bug introduced in logback version 0.9.12. Please refer to the the news page for precise details. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://qos.ch/mailman/listinfo/logback-announce -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

svn commit: r2067 - in logback/trunk: . logback-access logback-classic logback-core logback-examples logback-site
by noreply.ceki＠qos.ch 05 Dec '08

05 Dec '08

Author: ceki Date: Fri Dec 5 11:16:19 2008 New Revision: 2067 Modified: 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/pom.xml Log: - preparing release 0.9.13 Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Fri Dec 5 11:16:19 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12</version> + <version>0.9.13</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Fri Dec 5 11:16:19 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12</version> + <version>0.9.13</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Fri Dec 5 11:16:19 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12</version> + <version>0.9.13</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Fri Dec 5 11:16:19 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12</version> + <version>0.9.13</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Fri Dec 5 11:16:19 2008 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12</version> + <version>0.9.13</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Fri Dec 5 11:16:19 2008 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12</version> + <version>0.9.13</version> <packaging>pom</packaging> <name>Logback-Parent</name>

1 0

[JIRA] Created: (LBCLASSIC-91) Logger.setLevel(null) may throw NPE
by mateusz jedruch (JIRA) 05 Dec '08

05 Dec '08

Logger.setLevel(null) may throw NPE ----------------------------------- Key: LBCLASSIC-91 URL: http://jira.qos.ch/browse/LBCLASSIC-91 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.12 Reporter: mateusz jedruch Assignee: Logback dev list When setting null for logger which has childes with null levels then NPE is thrown: Caused by: java.lang.NullPointerException at ch.qos.logback.classic.Logger.handleParentLevelChange(Logger.java:216) [classes/:na] at ch.qos.logback.classic.Logger.setLevel(Logger.java:200) [classes/:na] .... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 5

svn commit: r2066 - in logback/trunk: logback-classic/src/test/java/ch/qos/logback/classic logback-site/src/site/pages
by noreply.ceki＠qos.ch 05 Dec '08

05 Dec '08

Author: ceki Date: Fri Dec 5 11:13:21 2008 New Revision: 2066 Modified: logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java logback/trunk/logback-site/src/site/pages/download.html logback/trunk/logback-site/src/site/pages/news.html Log: - blurb about LBCLASSIC-91 - preparing release 0.9.13 - minor doc changes Modified: logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java ============================================================================== --- logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java (original) +++ logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java Fri Dec 5 11:13:21 2008 @@ -193,9 +193,10 @@ @Test public void setLevelToNull_LBCLASSIC_91() { loggerTest.setLevel(Level.DEBUG); - lc.getLogger(loggerTest.getName() + ".child"); + ch.qos.logback.classic.Logger child = lc.getLogger(loggerTest.getName() + ".child"); loggerTest.setLevel(null); assertEquals(root.getEffectiveLevel(), loggerTest.getEffectiveLevel()); + assertEquals(root.getEffectiveLevel(), child.getEffectiveLevel()); } } Modified: logback/trunk/logback-site/src/site/pages/download.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/download.html (original) +++ logback/trunk/logback-site/src/site/pages/download.html Fri Dec 5 11:13:21 2008 @@ -38,10 +38,12 @@ A console plugin for Eclipse is also available. It allows you to recieve logging events in a convenient Eclipse view, and - offers, among other functionnalities, the powerful filtering - framework present in logback. A more precise description can be - found in the plugin's <a href="consolePlugin.html">user guide</a>. - + offers, among other features, integrates with logbacks filtering + framework. A more precise description can be found in the plugin's + <a href="consolePlugin.html">user guide</a>. Unfortunately, the + console plugin is somewhat outdated. It expects logback version + 0.9.9. It will be upgraded in the coming weeks. + <ul> <li> Modified: logback/trunk/logback-site/src/site/pages/news.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/news.html (original) +++ logback/trunk/logback-site/src/site/pages/news.html Fri Dec 5 11:13:21 2008 @@ -28,6 +28,16 @@ <hr width="80%" align="center" /> + + <h3>5th of December 2008 - Release of version 0.9.13</h3> + + A <code>NullPointerException</code> was being thrown when a the + level of a logger was set to null. The logger in question had to + have children. This problem was reported in <a + href="http://jira.qos.ch/browse/LBCLASSIC-91">LBCLASSIC-91</a> + by Mateusz Jedruch. + + <h3>4th of December 2008 - Release of version 0.9.12</h3> Fixed <a href="http://jira.qos.ch/browse/LBCORE-26">bug

1 0

svn commit: r2065 - in logback/trunk/logback-classic/src: main/java/ch/qos/logback/classic test/java/ch/qos/logback/classic
by noreply.ceki＠qos.ch 05 Dec '08

05 Dec '08

Author: ceki Date: Fri Dec 5 11:00:48 2008 New Revision: 2065 Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java Log: Fix LBCLASSIC-91 An NPE would be thrown when setting the level of a logger to null, if the logger in question had children. Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java Fri Dec 5 11:00:48 2008 @@ -163,12 +163,13 @@ } else { effectiveLevelInt = newLevel.levelInt; } + if (childrenList != null) { int len = childrenList.size(); for (int i = 0; i < len; i++) { Logger child = (Logger) childrenList.get(i); // tell child to handle parent levelInt change - child.handleParentLevelChange(newLevel); + child.handleParentLevelChange(effectiveLevelInt); } } } @@ -179,18 +180,18 @@ * * @param newParentLevel */ - private synchronized void handleParentLevelChange(Level newParentLevel) { + private synchronized void handleParentLevelChange(int newParentLevelInt) { // changes in the parent levelInt affect children only if their levelInt is // null if (level == null) { - effectiveLevelInt = newParentLevel.levelInt; + effectiveLevelInt = newParentLevelInt; // propagate the parent levelInt change to this logger's children if (childrenList != null) { int len = childrenList.size(); for (int i = 0; i < len; i++) { Logger child = (Logger) childrenList.get(i); - child.handleParentLevelChange(newParentLevel); + child.handleParentLevelChange(newParentLevelInt); } } } Modified: logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java ============================================================================== --- logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java (original) +++ logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/LoggerTest.java Fri Dec 5 11:00:48 2008 @@ -189,4 +189,13 @@ loggerTest.setLevel(null); assertEquals(root.getEffectiveLevel(), loggerTest.getEffectiveLevel()); } + + @Test + public void setLevelToNull_LBCLASSIC_91() { + loggerTest.setLevel(Level.DEBUG); + lc.getLogger(loggerTest.getName() + ".child"); + loggerTest.setLevel(null); + assertEquals(root.getEffectiveLevel(), loggerTest.getEffectiveLevel()); + } + }

1 0

Release of logback version 0.9.12
by Ceki Gulcu 05 Dec '08

05 Dec '08

4th of December 2008 - Release of version 0.9.12 After a lull of one month, I am happy to announce the release of logback version 0.9.12. This version includes both bug fixes as well as significant enhancements. Here is the list: Fixed bug LBCORE-26 reported by Tsutomu YANO and independently by Hontvári József and Gamaliel Amaudruz. RollingFileAppender when used in conjunction with DateBasedRollingPolicy will rollover existing log files at initialization if their timestamp warrants it. Added support for file appending in prudent mode. Thus, multiple FileAppender instances running on multiple JVMs can safely write to the same log file. With certain limitations, prudent mode extends to RollingFileAppender. Fixed LBCLASSIC-83. It is now possible to set the level of a logger to null, even if it was previously set to a non-null level. Previously, a NullPointerException would be thrown. In reponse to LBCLASSIC-61, LBCLASSIC-33, LBCLASSIC-24 and LBCLASSIC-14 JMXConfigurator has been redesigned. Fixed LBGENERAL-22. The log4j.properties translator web-application has been significatnly refactored. Fixed improvement request LBCLASSIC-59 relation to StatusListeners, originally submitted by Anton Tagunov. The logger and class name converters now consider zero as having special meaning, and will return the simple class name, removing the package name prefix. This feature was asked by Silvano Maffeis. In response to LBCLASSIC-54 support for turbo filters has refactored. The present code is safe under concurrent access while still offering good performance. Fixed LBCORE-43 reported by Bruno Navert. Configuration files can now look up property files from classpath resources. Fixed LBCLASSIC-86 related to AccessControlException thrown when run in a JVM with a SecurityManager. Invoking the LoggerContext.reset() method resets logger levels to their default value, that is DEBUG for the root logger and null for all other loggers. This was requested in LBCLASSIC-90 by Mateusz Jedruch. Fixed bug LBCLASSIC-69 reported by Anton Tagunov. The LevelToSyslogSeverity now correctly handles the TRACE level. Fixed bug LBCLASSIC-57 reported by Anton Tagunov. SyslogAppender could overwhelm the Syslog server with very large messages. SyslogAppender now limits its message size to 256K. Logback now supports setting the logger context name as well as inserting variables stored in JNDI as properties. Fixed issue LBCLASSIC-49 reported by Oliver Lietz. The getLogger() method in LoggerContext class will now throw an IllegalArgumentException when invoked with a null argument. You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://qos.ch/mailman/listinfo/logback-announce Enjoy, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

2 1

svn commit: r2064 - in logback/trunk/logback-site/src/site/pages: . manual
by noreply.ceki＠qos.ch 04 Dec '08

04 Dec '08

Author: ceki Date: Thu Dec 4 23:40:57 2008 New Revision: 2064 Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html logback/trunk/logback-site/src/site/pages/news.html Log: minor doc changes Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/joran.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/joran.html Thu Dec 4 23:40:57 2008 @@ -1231,10 +1231,10 @@ variables from JNDI</a></h3> Under certain circumstances, you may want to make use of - env-entries in JNDI. The <code><insertFromJNDI></code> - configuration directive extracts an env-entry from JNDI and inserts - it as variable specified by the as - attribute. + env-entries stored in JNDI. The <code><insertFromJNDI></code> + configuration directive extracts an env-entry stored in JNDI and + inserts it as variable as specified by the as attribute. Example 3.: Insert as properties env-entries obtained via JNDI Modified: logback/trunk/logback-site/src/site/pages/news.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/news.html (original) +++ logback/trunk/logback-site/src/site/pages/news.html Thu Dec 4 23:40:57 2008 @@ -117,6 +117,12 @@ now limits its message size to 256K. + Logback now supports <a + href="manual/joran.html#contextName">setting the logger context + name</a> as well as inserting variables <a + href="manual/joran.html#insertFromJNDI">stored in JNDI</a> as + properties. + Fixed issue <a href="http://jira.qos.ch/browse/LBCLASSIC-49">LBCLASSIC-49</a>

1 0

svn commit: r2063 - in logback/trunk: . logback-access logback-classic logback-core logback-examples logback-site
by noreply.ceki＠qos.ch 04 Dec '08

04 Dec '08

Author: ceki Date: Thu Dec 4 23:34:41 2008 New Revision: 2063 Modified: 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/pom.xml Log: preparing release 0.9.12 Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Thu Dec 4 23:34:41 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12-SNAPSHOT</version> + <version>0.9.12</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Thu Dec 4 23:34:41 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12-SNAPSHOT</version> + <version>0.9.12</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Thu Dec 4 23:34:41 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12-SNAPSHOT</version> + <version>0.9.12</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Thu Dec 4 23:34:41 2008 @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12-SNAPSHOT</version> + <version>0.9.12</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Thu Dec 4 23:34:41 2008 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12-SNAPSHOT</version> + <version>0.9.12</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Thu Dec 4 23:34:41 2008 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.12-SNAPSHOT</version> + <version>0.9.12</version> <packaging>pom</packaging> <name>Logback-Parent</name>

1 0

svn commit: r2062 - logback/trunk/logback-examples/lib
by noreply.ceki＠qos.ch 04 Dec '08

04 Dec '08

Author: ceki Date: Thu Dec 4 23:15:43 2008 New Revision: 2062 Modified: logback/trunk/logback-examples/lib/ (props changed) Log: ignore jar file copied during build

1 0

svn commit: r2061 - in logback/trunk: . logback-classic logback-examples logback-examples/src/main/java/chapter3 logback-site/src/site/pages logback-site/src/site/pages/css logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 04 Dec '08

04 Dec '08

Author: ceki Date: Thu Dec 4 23:14:25 2008 New Revision: 2061 Added: logback/trunk/logback-examples/src/main/java/chapter3/contextName.xml logback/trunk/logback-examples/src/main/java/chapter3/insertFromJNDI.xml Modified: logback/trunk/logback-classic/pom.xml logback/trunk/logback-examples/pom.xml logback/trunk/logback-site/src/site/pages/css/common.css logback/trunk/logback-site/src/site/pages/faq.html logback/trunk/logback-site/src/site/pages/manual/architecture.html logback/trunk/logback-site/src/site/pages/manual/joran.html logback/trunk/logback-site/src/site/pages/manual/layouts.html logback/trunk/logback-site/src/site/pages/news.html logback/trunk/pom.xml Log: - removed slf4j-ext declaration from the parent pom. In child modules the slf4j-ext was being inserted in compile scope instead of test scope. - updated documentation in relation to contextName and insertFromJNDI configuration directives. Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Thu Dec 4 23:14:25 2008 @@ -48,6 +48,7 @@ <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-ext</artifactId> + <version>${slf4j.version}</version> <scope>test</scope> </dependency> @@ -62,6 +63,7 @@ <dependency> <groupId>org.slf4j</groupId> <artifactId>log4j-over-slf4j</artifactId> + <version>${slf4j.version}</version> <scope>test</scope> </dependency> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Thu Dec 4 23:14:25 2008 @@ -48,6 +48,7 @@ <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-ext</artifactId> + <version>${slf4j.version}</version> </dependency> <dependency> Added: logback/trunk/logback-examples/src/main/java/chapter3/contextName.xml ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter3/contextName.xml Thu Dec 4 23:14:25 2008 @@ -0,0 +1,15 @@ +<configuration> + + <contextName>myAppName</contextName> + + <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%d %contextName [%t] %level %logger{36} - %msg%n</Pattern> + </layout> + </appender> + + <root level="debug"> + <appender-ref ref="STDOUT" /> + </root> + +</configuration> \ No newline at end of file Added: logback/trunk/logback-examples/src/main/java/chapter3/insertFromJNDI.xml ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter3/insertFromJNDI.xml Thu Dec 4 23:14:25 2008 @@ -0,0 +1,16 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<configuration> + <insertFromJNDI env-entry-name="java:comp/env/appName" as="appName" /> + <contextName>${appName}</contextName> + + <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%d %contextName %level %msg %logger{50}%n</Pattern> + </layout> + </appender> + + <root level="DEBUG"> + <appender-ref ref="CONSOLE" /> + </root> +</configuration> Modified: logback/trunk/logback-site/src/site/pages/css/common.css ============================================================================== --- logback/trunk/logback-site/src/site/pages/css/common.css (original) +++ logback/trunk/logback-site/src/site/pages/css/common.css Thu Dec 4 23:14:25 2008 @@ -100,7 +100,7 @@ font-size: smaller; } -strong { +.strong { /*font-size: 13px;*/ font-weight: bold; } @@ -198,6 +198,13 @@ font-family: Courier, monospace; } +.variable { + font-family: Courier, monospace; + font-style:italic; +} + + + .attr { font-family: Courier, monospace; font-style:italic; Modified: logback/trunk/logback-site/src/site/pages/faq.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/faq.html (original) +++ logback/trunk/logback-site/src/site/pages/faq.html Thu Dec 4 23:14:25 2008 @@ -54,6 +54,12 @@ </li> <li> + <a href="#overrideFromCL"> + How can I disable logging from the command line? + </a> + </li> + + <li> <a href="#setup_jetty">How can Jetty be instructed to use logback-classic as its logging implementataion? </a> @@ -190,6 +196,49 @@  + + <dt> + <a name="overrideFromCL" href="#overrideFromCL"> + How can I disable logging from the command line? + </a> + </dt> + <dd> + Logback does not allow disabling logging from the command + line. However, if the configuration file allows it, you can + set the level of logers on the command line via a java + system property. Here is such a configuration file. + + <configuration> + <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%d [%thread] %level %logger - %m%n</Pattern> + </layout> + </appender> + <root level="${root-level:-INFO}"> + <appender-ref ref="CONSOLE"/> + </root> +</configuration> + + + Making use of <a + href="manual/joran.html#variableSubstitution">variable + substitution</a> as well as <a + href="manual/joran.html#defaultValuesForVariables">default + values for variables</a>, if the root-level system property is set to + <code>OFF</code>, then all logging will be turned + off. However, if it is not set, it will assume the default + value of <code>INFO</code>. Note that you can set the root-level system property to any + level value of your choice. The value <code>OFF</code> is + just an example. + + + <hr/> + </dd> + + +  <dt> <a name="setup_jetty" href="#"> Modified: logback/trunk/logback-site/src/site/pages/manual/architecture.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/architecture.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/architecture.html Thu Dec 4 23:14:25 2008 @@ -77,11 +77,12 @@ The <code>Logger</code> class is part of the logback-classic module. On the other hand, the <code>Appender</code> and <code>Layout</code> interfaces are part of logback-core. As a - general-purpose module, logback-core has no notion of loggers. + general-purpose module, logback-core has no notion of + loggers. - <a name="LoggerContext"></a> - <h3>Logger context</h3> + <h3><a name="LoggerContext" href="#LoggerContext">Logger + context</a></h3> The first and foremost advantage of any logging API over plain <code>System.out.println</code> resides in its ability to disable @@ -89,13 +90,16 @@ unhindered. This capability assumes that the logging space, that is, the space of all possible logging statements, is categorized according to some developer-chosen criteria. In logback-classic, - this categorization is an inherent part of loggers. + this categorization is an inherent part of loggers. Every single + loggers is attached to a <code>LoggerContext</code> which is + responsible for manufacturing loggers as well as arranging them in + a tree like hierarchy. - - Loggers are named entities. Their names are case-sensitive and - they follow the hierarchical naming rule: + Loggers are named entities. Their names are case-sensitive and + they follow the hierarchical naming rule: + <div class="definition"> <div class="deftitle">Named Hierarchy</div> @@ -107,44 +111,42 @@ </div> - - For example, the logger named <code>"com.foo"</code> - is a parent of the logger named <code>"com.foo.Bar"</code>. - Similarly, <code>"java"</code> - is a parent of <code>"java.util"</code> and an ancestor of - <code>"java.util.Vector"</code>. - This naming scheme should be familiar to most developers. + For example, the logger named <code>"com.foo"</code> is a + parent of the logger named <code>"com.foo.Bar"</code>. Similarly, + <code>"java"</code> is a parent of <code>"java.util"</code> and an + ancestor of <code>"java.util.Vector"</code>. This naming scheme + should be familiar to most developers. - - The root logger resides at the top of the logger hierarchy. It - is exceptional in that it is part of every hierarchy at its - inception. Like every logger, it can be retrieved by its name, - as follows: + + The root logger resides at the top of the logger hierarchy. It + is exceptional in that it is part of every hierarchy at its + inception. Like every logger, it can be retrieved by its name, as + follows: - <div class="source"><pre>Logger rootLogger = LoggerFactory.getLogger(<a href="../apidocs/constant-values.html#ch.qos.logback.classic.LoggerContext.ROOT_NAME">LoggerContext.ROOT_NAME</a>);</pre></div> + + Logger rootLogger = LoggerFactory.getLogger(<a href="../apidocs/constant-values.html#ch.qos.logback.classic.LoggerContext.ROOT_NAME">LoggerContext.ROOT_NAME</a>); - - All other loggers are also retrieved with the class static - <code>getLogger</code> method found in the <a - href="http://www.slf4j.org/api/org/slf4j/Logger.html">org.slf4j.LoggerFactory</a> - class. This method takes the name of the desired logger as a - parameter. Some of the basic methods in the <code>Logger</code> - interface are listed below. + All other loggers are also retrieved with the class static + <code>getLogger</code> method found in the <a + href="http://www.slf4j.org/api/org/slf4j/Logger.html">org.slf4j.LoggerFactory</a> + class. This method takes the name of the desired logger as a + parameter. Some of the basic methods in the <code>Logger</code> + interface are listed below. - <div class="source"><pre>package org.slf4j; + package org.slf4j; public interface Logger { // Printing methods: + public void trace(String message); public void debug(String message); public void info(String message); public void warn(String message); public void error(String message); - public void fatal(String message); -}</pre></div> +} Loggers may be assigned levels. The set of possible levels, - that is DEBUG, INFO, WARN and ERROR are defined in the + that is TRACE, DEBUG, INFO, WARN and ERROR are defined in the <code>ch.qos.logback.classic.Level</code> class. Note that in logback, the level class is final and cannot be derived, as a much more flexible approach exist in the form of <code>Marker</code> @@ -166,15 +168,13 @@ </div> - - To ensure that all loggers can eventually inherit a level, the - root logger always has an assigned level. By default, this level - is DEBUG. - - - Below are four examples with various assigned level values and - the resulting effective (inherited) levels according to the - level inheritance rule. + To ensure that all loggers can eventually inherit a level, the + root logger always has an assigned level. By default, this level + is DEBUG. + + Below are four examples with various assigned level values and + the resulting effective (inherited) levels according to the level + inheritance rule. Example 1 Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/joran.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/joran.html Thu Dec 4 23:14:25 2008 @@ -1148,8 +1148,9 @@ "golden". - <a name="Include"></a> - <h3>File inclusion</h3> + + <h3><a name="fileInclusion" href="#fileInclusion">File + inclusion</a></h3> Joran supports including parts of a configuration file from another file. This is done by declaring a <code><include></code> @@ -1192,8 +1193,75 @@ + <h3><a name="contextName" href="#contextName">Setting the context name</a></h3> + As mentioned <a href="architecture.html#LoggerContext">in an + earlier chapter</a>, every logger is attached to logger context. By + default, the logger context is called "default". However, you can + set a different name with the help of the + <code><contextName></code> configuration directive. Note that + once set, the logger context name <a + href="../apidocs/ch/qos/logback/core/ContextBase.html#setName(java.lang.String)">cannot + be changed</a>. Setting the context name is a simple and + straightforward method in order to distinguish between multiple + applications logging to the same target. + + + Example 3.: Set the context name and display it + (logback-examples/src/main/java/chapter3/contextName.xml) + <configuration> + <contextName>myAppName</contextName> + <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%d %contextName [%t] %level %logger{36} - %msg%n</Pattern> + </layout> + </appender> + + <root level="debug"> + <appender-ref ref="STDOUT" /> + </root> +</configuration> + + This last examples illustrates naming of the logger + context. Adding the the <a + href="layouts.html#conversionWord">contextName conversion word</a> + in layout's pattern will output the said name. + + <h3><a name="insertFromJNDI" href="#insertFromJNDI">Obtaining + variables from JNDI</a></h3> + + Under certain circumstances, you may want to make use of + env-entries in JNDI. The <code><insertFromJNDI></code> + configuration directive extracts an env-entry from JNDI and inserts + it as variable specified by the as + attribute. + + + Example 3.: Insert as properties env-entries obtained via JNDI + (logback-examples/src/main/java/chapter3/insertFromJNDI.xml) + <configuration> + <insertFromJNDI env-entry-name="java:comp/env/appName" as="appName" /> + <contextName>${appName}</contextName> + + <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%d %contextName %level %msg %logger{50}%n</Pattern> + </layout> + </appender> + + <root level="DEBUG"> + <appender-ref ref="CONSOLE" /> + </root> +</configuration> + + In this last example, the "java:comp/env/appName" env-entry is + inserted as the appName property. Note + that the <code><contextName></code> directive sets the context + name based on the value of the appName + property inserted by the previous <code><insertFromJNDI></code> + directive.. + <script src="../templates/footer.js" type="text/javascript"></script> </div> Modified: logback/trunk/logback-site/src/site/pages/manual/layouts.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/layouts.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/layouts.html Thu Dec 4 23:14:25 2008 @@ -382,7 +382,7 @@ <table class="bodyTable properties" border="0"> <tr> - <th>Conversion Word</th> + <th><a name="conversionWord" href="#conversionWord">Conversion Word</a></th> <th>Effect</th> </tr> @@ -477,12 +477,20 @@ </td> </tr> - <tr> + <tr> + <td align="center"> + contextName + cn </td> + <td>Outputs the name of the logger context to which the + logger at the origin of the logging event is attached + to. </td> + </tr> + <tr class="alt"> <td align="center"> d{pattern} date{pattern} </td> - <td> + <td > Used to output the date of the logging event. The date conversion word may be followed by an option enclosed between braces. @@ -524,7 +532,7 @@ </td> </tr> - <tr class="alt"> + <tr> <td align="center"> F / file </td> @@ -541,7 +549,7 @@ </td> </tr> - <tr> + <tr class="alt"> <td align="center"> caller{depth} caller{depth, evaluator-1, ... evaluator-n} @@ -591,7 +599,7 @@ </td> </tr> - <tr class="alt"> + <tr> <td align="center"> L / line </td> @@ -610,7 +618,7 @@ </tr> - <tr> + <tr class="alt"> <td align="center"> m / msg / message </td> @@ -620,7 +628,7 @@ </td> </tr> - <tr class="alt"> + <tr> <td align="center"> M / method </td> @@ -638,7 +646,7 @@ </td> </tr> - <tr> + <tr class="alt"> <td align="center"> n </td> @@ -659,14 +667,14 @@ </tr> - <tr class="alt"> + <tr> <td align="center"> p / le / level </td> <td>Used to output the level of the logging event.</td> </tr> - <tr> + <tr class="alt"> <td align="center"> r / relative @@ -680,7 +688,7 @@ </tr> - <tr class="alt"> + <tr> <td align="center"> t / thread </td> @@ -692,7 +700,7 @@ </tr> - <tr> + <tr class="alt"> <td align="center"> X{key} mdc{key} @@ -721,7 +729,7 @@ </td> </tr> - <tr class="alt"> + <tr> <td align="center"> ex{length} exception{length} @@ -801,8 +809,7 @@ </td> </tr> - - <tr> + <tr class="alt"> <td align="center"> xEx{length} xException{length} @@ -856,10 +863,9 @@ </td> - </tr> - <tr class="b"> + <tr> <td align="center"> nopex nopexception @@ -879,7 +885,7 @@ </td> </tr> - <tr class="a"> + <tr class="alt"> <td align="center"> marker </td> Modified: logback/trunk/logback-site/src/site/pages/news.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/news.html (original) +++ logback/trunk/logback-site/src/site/pages/news.html Thu Dec 4 23:14:25 2008 @@ -96,6 +96,13 @@ a JVM with a <code>SecurityManager</code>. + Invoking the <code>LoggerContext.reset()</code> method resets + logger levels to their default value, that is <code>DEBUG</code> + for the root logger and <code>null</code> for all other + loggers. This was requested in <a + href="http://jira.qos.ch/browse/LBCLASSIC-90">LBCLASSIC-90</a> by + Mateusz Jedruch. +  Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Thu Dec 4 23:14:25 2008 @@ -73,17 +73,6 @@ <version>${slf4j.version}</version> </dependency> <dependency> - <groupId>org.slf4j</groupId> - <artifactId>log4j-over-slf4j</artifactId> - <version>${slf4j.version}</version> - </dependency> - <dependency> - <groupId>org.slf4j</groupId> - <artifactId>slf4j-ext</artifactId> - <version>${slf4j.version}</version> - </dependency> - - <dependency> <groupId>janino</groupId> <artifactId>janino</artifactId> <version>2.4.3</version>

1 0