- logback-dev - mailman3.qos.ch

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-14-g5ca0580
by git-noreply＠pixie.qos.ch 01 Feb '10

01 Feb '10

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 5ca0580bc65b84cc7ee444abf1fda2fcf4e60f60 (commit) from 622907388d4146b399842313a3f9aec97ad2dd75 (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=5ca0580bc65b84cc7ee444ab… http://github.com/ceki/logback/commit/5ca0580bc65b84cc7ee444abf1fda2fcf4e60… commit 5ca0580bc65b84cc7ee444abf1fda2fcf4e60f60 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Feb 1 22:31:13 2010 +0100 - updated access.html docs to conform with Tomcat 6.0 and not 5.5. diff --git a/logback-site/src/site/pages/access.html b/logback-site/src/site/pages/access.html index f579138..de0002c 100644 --- a/logback-site/src/site/pages/access.html +++ b/logback-site/src/site/pages/access.html @@ -45,23 +45,23 @@ <h1>Logback-access under Tomcat</h1> <p>To use logback-access with Tomcat, after downlading the logback - distribution, place the files <em>logback-core-VERSION.jar</em> - and <em>logback-access-VERSION.jar</em> under + distribution, place the files <em>logback-core-${project.version}.jar</em> + and <em>logback-access-${project.version}.jar</em> under $TOMCAT_HOME/<b>server/lib/</b> directory, where $TOMCAT_HOME is the folder where you have installed Tomcat. We have tested - logback-access module with Tomcat version 5.5.26. + logback-access with Tomcat versions 5.5.26 and 6.0.20. </p> - <p>If you place the logback-core and logback-access jars in - $TOMCAT_HOME/server/lib <em>and</em> your webapps do not use + <p>Place the logback-core and logback-access jars in + $TOMCAT_HOME/lib <em>and</em> your webapps do not use logback-classic, then everything should be fine. If however your - webapps do indeed use logback-classic, you must make sure to - bundle <code>logback-core.jar</code> under your webapps' - WEB-INF/lib directory. An alternative strategy is to place - logback-core.jar under $TOMCAT_HOME/common/lib. In that case, you - no longer need to place logback-core.jar in your web-apps. + webapps do indeed use logback-classic, in addition to + <em>logback-classic.jar</em>,w make sure to bundle + <code>logback-core.jar</code> under your webapps' WEB-INF/lib + directory as well. </p> + <h2>LogbackValve</h2> <p>The <a @@ -79,7 +79,8 @@ </p> <div class="source"><pre><Valve className="ch.qos.logback.access.tomcat.LogbackValve"/></pre></div> - <p>This line is usually nested within an <em>Engine</em> element. + <p>This line is usually nested within an <code><Engine></code> + or <code><Host></code> element. </p> <p>By default, <code>LogbackValve</code> looks for a configuration @@ -93,7 +94,7 @@ </p> <p>In order to help with troubleshooting, by default, the - LogbackValve will print its internal status at its + <code>LogbackValve</code> will print its internal status at its initialization. Typical output would look as: </p> @@ -292,7 +293,7 @@ </rollingPolicy> <layout class="ch.qos.logback.access.PatternLayout"> - <Pattern">combined</Pattern"> + <Pattern>combined</Pattern> </layout> </appender> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/access.html | 27 ++++++++++++++------------- 1 files changed, 14 insertions(+), 13 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

RFC 5424 and Structured Data support.
by Ralph Goers 29 Jan '10

29 Jan '10

I would appreciate it if you would review git://github.com/rgoers/logback.git and git://github.com/rgoers/slf4j.git and incorporate that into the "official" logback source. The forks include fixes for LBCLASSIC-116, LBCLASSIC-154, possibly LBCLASSIC-153. The SLF4J changes include support LBCLASSIC-116 by way of fixing SLF4J bug 148 and also includes fixes for SLF4J bugs 31 and 127. Both of my forks include all of the latest changes in your forks. Ralph

6 29

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-13-g6229073
by git-noreply＠pixie.qos.ch 28 Jan '10

28 Jan '10

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 622907388d4146b399842313a3f9aec97ad2dd75 (commit) from 705c0faec81a065b90a8bdbf6497c122e734aace (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=622907388d4146b399842313… http://github.com/ceki/logback/commit/622907388d4146b399842313a3f9aec97ad2d… commit 622907388d4146b399842313a3f9aec97ad2dd75 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Jan 28 08:27:58 2010 +0100 minor comment correction diff --git a/logback-core/src/main/java/ch/qos/logback/core/db/dialect/DBUtil.java b/logback-core/src/main/java/ch/qos/logback/core/db/dialect/DBUtil.java index eb8294b..330b573 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/db/dialect/DBUtil.java +++ b/logback-core/src/main/java/ch/qos/logback/core/db/dialect/DBUtil.java @@ -94,7 +94,7 @@ public class DBUtil extends ContextAwareBase { public boolean supportsGetGeneratedKeys(DatabaseMetaData meta) { try { // - // invoking JDK 1.4 method by reflection + // invoking JDBC 1.4 method by reflection // return ((Boolean) DatabaseMetaData.class.getMethod( "supportsGetGeneratedKeys", (Class[]) null).invoke(meta, ----------------------------------------------------------------------- Summary of changes: .../ch/qos/logback/core/db/dialect/DBUtil.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-12-g705c0fa
by git-noreply＠pixie.qos.ch 28 Jan '10

28 Jan '10

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 705c0faec81a065b90a8bdbf6497c122e734aace (commit) from 7172853f27b3339eb1c1790f96f46c0162bdf141 (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=705c0faec81a065b90a8bdbf… http://github.com/ceki/logback/commit/705c0faec81a065b90a8bdbf6497c122e734a… commit 705c0faec81a065b90a8bdbf6497c122e734aace Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Jan 28 08:11:56 2010 +0100 - added missing hsqldb.sql files. A live version of these files can be found in DBAppenderTestFixture.java in the ch.qos.logback.access.db and ch.qos.logback.classic.db packages under src/test. diff --git a/logback-access/src/main/java/ch/qos/logback/access/db/dialect/hsqldb.sql b/logback-access/src/main/java/ch/qos/logback/access/db/dialect/hsqldb.sql new file mode 100644 index 0000000..c82b677 --- /dev/null +++ b/logback-access/src/main/java/ch/qos/logback/access/db/dialect/hsqldb.sql @@ -0,0 +1,28 @@ +# This SQL script creates the required tables by ch.qos.logback.access.db.DBAppender +# +# It is intended for HSQL databases. + + +DROP TABLE access_event_header IF EXISTS; +DROP TABLE access_event IF EXISTS; + +CREATE TABLE access_event ( + timestmp BIGINT NOT NULL, + requestURI VARCHAR(254), + requestURL VARCHAR(254), + remoteHost VARCHAR(254), + remoteUser VARCHAR(254), + remoteAddr VARCHAR(254), + protocol VARCHAR(254), + method VARCHAR(254), + serverName VARCHAR(254), + postContent VARCHAR(254), + event_id INT NOT NULL IDENTITY); + + +CREATE TABLE access_event_header ( + event_id INT NOT NULL, + header_key VARCHAR(254) NOT NULL, + header_value LONGVARCHAR, + PRIMARY KEY(event_id, header_key), + FOREIGN KEY (event_id) REFERENCES access_event(event_id)); \ No newline at end of file diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/db/dialect/hsqldb.sql b/logback-classic/src/main/java/ch/qos/logback/classic/db/dialect/hsqldb.sql new file mode 100644 index 0000000..3cdeccc --- /dev/null +++ b/logback-classic/src/main/java/ch/qos/logback/classic/db/dialect/hsqldb.sql @@ -0,0 +1,35 @@ +# This SQL script creates the required tables by ch.qos.logback.classic.db.DBAppender. +# +# It is intended for HSQL databases. It has been tested on HSQL 1.8.07. + +DROP TABLE logging_event_exception IF EXISTS; +DROP TABLE logging_event_property IF EXISTS; +DROP TABLE logging_event IF EXISTS; + +CREATE TABLE logging_event ( + timestmp BIGINT NOT NULL, + formatted_message LONGVARCHAR NOT NULL, + logger_name VARCHAR(256) NOT NULL, + level_string VARCHAR(256) NOT NULL, + thread_name VARCHAR(256), + reference_flag SMALLINT, + caller_filename VARCHAR(256), + caller_class VARCHAR(256), + caller_method VARCHAR(256), + caller_line CHAR(4), + event_id INT NOT NULL IDENTITY); + + +CREATE TABLE logging_event_property ( + event_id INT NOT NULL, + mapped_key VARCHAR(254) NOT NULL, + mapped_value LONGVARCHAR, + PRIMARY KEY(event_id, mapped_key), + FOREIGN KEY (event_id) REFERENCES logging_event(event_id)); + +CREATE TABLE logging_event_exception ( + event_id INT NOT NULL, + i SMALLINT NOT NULL, + trace_line VARCHAR(256) NOT NULL, + PRIMARY KEY(event_id, i), + FOREIGN KEY (event_id) REFERENCES logging_event(event_id)); \ No newline at end of file ----------------------------------------------------------------------- Summary of changes: .../ch/qos/logback/access/db/dialect/hsqldb.sql | 28 ++++++++++++++++ .../ch/qos/logback/classic/db/dialect/hsqldb.sql | 35 ++++++++++++++++++++ 2 files changed, 63 insertions(+), 0 deletions(-) create mode 100644 logback-access/src/main/java/ch/qos/logback/access/db/dialect/hsqldb.sql create mode 100644 logback-classic/src/main/java/ch/qos/logback/classic/db/dialect/hsqldb.sql hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-181) java.lang.NoClassDefFoundError: org/codehaus/janino/ExpressionEvaluator if use ch.qos.logback.core.filter.EvaluatorFilter
by Dmitry Smirnov (JIRA) 26 Jan '10

26 Jan '10

java.lang.NoClassDefFoundError: org/codehaus/janino/ExpressionEvaluator if use ch.qos.logback.core.filter.EvaluatorFilter ------------------------------------------------------------------------------------------------------------------------- Key: LBCLASSIC-181 URL: http://jira.qos.ch/browse/LBCLASSIC-181 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.18 Environment: windows7 enterprise Reporter: Dmitry Smirnov Assignee: Logback dev list After using filter with class ch.qos.logback.core.filter.EvaluatorFilter rised an exception without janino.jar is on the classpath, but janino is not mentioned in the documentation and examples. Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.NoClassDefFoundError: org/codehaus/janino/ExpressionEvaluator at ch.qos.logback.core.boolex.JaninoEventEvaluatorBase.start(JaninoEventEvaluatorBase.java:58) at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:168) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:311) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:191) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:178) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:328) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:60) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:121) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:89) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:60) at org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:230) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:112) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:248) at test.Ex1.<clinit>(Ex1.java:16) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:107) Caused by: java.lang.ClassNotFoundException: org.codehaus.janino.ExpressionEvaluator at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:303) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316) ... 23 more ch.qos.logback.core.boolex.JaninoEventEvaluatorBase has link on org.codehaus.janino.ExpressionEvaluator -- 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 1

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-11-g7172853
by git-noreply＠pixie.qos.ch 26 Jan '10

26 Jan '10

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 7172853f27b3339eb1c1790f96f46c0162bdf141 (commit) from 3b58f83f64a4b00f17505f112cd5831232ae4a8b (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=7172853f27b3339eb1c1790f… http://github.com/ceki/logback/commit/7172853f27b3339eb1c1790f96f46c0162bdf… commit 7172853f27b3339eb1c1790f96f46c0162bdf141 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Jan 26 21:59:45 2010 +0100 - In logback-classic ConfigurationAction, the HOSTNAME property is now automatically defined and added to the logger context. This value comes in handy in a variety of situations. diff --git a/logback-access/src/main/java/ch/qos/logback/access/joran/action/ConfigurationAction.java b/logback-access/src/main/java/ch/qos/logback/access/joran/action/ConfigurationAction.java index ed776dc..7e766f0 100644 --- a/logback-access/src/main/java/ch/qos/logback/access/joran/action/ConfigurationAction.java +++ b/logback-access/src/main/java/ch/qos/logback/access/joran/action/ConfigurationAction.java @@ -17,6 +17,7 @@ import org.xml.sax.Attributes; import ch.qos.logback.core.joran.action.Action; import ch.qos.logback.core.joran.spi.InterpretationContext; +import ch.qos.logback.core.util.ContextUtil; import ch.qos.logback.core.util.StatusPrinter; @@ -36,6 +37,8 @@ public class ConfigurationAction extends Action { debugMode = true; } + new ContextUtil(context).addHostNameAsProperty(); + // the context is appender attachable, so it is pushed on top of the stack ec.pushObject(getContext()); } diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/ConfigurationAction.java b/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/ConfigurationAction.java index 6475778..3eef4b4 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/ConfigurationAction.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/ConfigurationAction.java @@ -19,6 +19,7 @@ import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter; import ch.qos.logback.core.joran.action.Action; import ch.qos.logback.core.joran.spi.InterpretationContext; +import ch.qos.logback.core.util.ContextUtil; import ch.qos.logback.core.util.Duration; import ch.qos.logback.core.util.OptionHelper; import ch.qos.logback.core.util.StatusPrinter; @@ -38,14 +39,13 @@ public class ConfigurationAction extends Action { || debugAttrib.equalsIgnoreCase("null")) { addInfo(INTERNAL_DEBUG_ATTR + " attribute not set"); } else { - // LoggerContext loggerContext = (LoggerContext) context; - // ConfiguratorBase.attachTemporaryConsoleAppender(context); - debugMode = true; } processScanAttrib(attributes); + new ContextUtil(context).addHostNameAsProperty(); + // the context is turbo filter attachable, so it is pushed on top of the // stack ec.pushObject(getContext()); diff --git a/logback-core/src/main/java/ch/qos/logback/core/CoreConstants.java b/logback-core/src/main/java/ch/qos/logback/core/CoreConstants.java index ac1d8fd..a57425f 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/CoreConstants.java +++ b/logback-core/src/main/java/ch/qos/logback/core/CoreConstants.java @@ -104,4 +104,11 @@ public class CoreConstants { // configuration, then file.getURL() is registered public static String URL_OF_LAST_CONFIGURATION_VIA_JORAN = "URL_OF_LAST_CONFIGURATION_VIA_JORAN"; + + /** + * The key under which the local host name is registered in the logger + * context. + */ + public static final String HOSTNAME_KEY = "HOSTNAME"; + } diff --git a/logback-core/src/main/java/ch/qos/logback/core/util/ContextUtil.java b/logback-core/src/main/java/ch/qos/logback/core/util/ContextUtil.java new file mode 100644 index 0000000..f10afcb --- /dev/null +++ b/logback-core/src/main/java/ch/qos/logback/core/util/ContextUtil.java @@ -0,0 +1,42 @@ +/** + * Logback: the reliable, generic, fast and flexible logging framework. + * Copyright (C) 1999-2010, QOS.ch. All rights reserved. + * + * This program and the accompanying materials are dual-licensed under either + * the terms of the Eclipse Public License v1.0 as published by the Eclipse + * Foundation + * + * or (per the licensee's choosing) + * + * under the terms of the GNU Lesser General Public License version 2.1 as + * published by the Free Software Foundation. + */ +package ch.qos.logback.core.util; + +import java.net.InetAddress; +import java.net.UnknownHostException; + +import ch.qos.logback.core.Context; +import ch.qos.logback.core.CoreConstants; +import ch.qos.logback.core.spi.ContextAwareBase; + +public class ContextUtil extends ContextAwareBase { + + public ContextUtil(Context context) { + setContext(context); + } + + /** + * Add the local host's name as a property + */ + public void addHostNameAsProperty() { + try { + InetAddress localhost = InetAddress.getLocalHost(); + context.putProperty(CoreConstants.HOSTNAME_KEY, localhost.getHostName()); + } catch (UnknownHostException e) { + addError("Failed to get local hostname", e); + } catch (SecurityException e) { + addError("Failed to get local hostname", e); + } + } +} diff --git a/logback-core/src/main/java/ch/qos/logback/core/util/SystemInfo.java b/logback-core/src/main/java/ch/qos/logback/core/util/SystemInfo.java index e2d701f..e423939 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/util/SystemInfo.java +++ b/logback-core/src/main/java/ch/qos/logback/core/util/SystemInfo.java @@ -13,10 +13,12 @@ */ package ch.qos.logback.core.util; -public class SystemInfo { + +public class SystemInfo { public static String getJavaVendor() { return OptionHelper.getSystemProperty("java.vendor", null); } + } diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 169360a..d3a135e 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -1148,7 +1148,8 @@ public class MyApp3 { sequence. For example, if <em>java.home.dir</em> system property is set to <em>/home/xyz</em>, then every occurrence of the sequence <em>${java.home.dir}</em> will be interpreted as <em>/home/xyz</em>. - </p> + As it often comes in handy, the variable ${HOSTNAME} is + automatically defined.</p> <h4>properties are inserted into the logger context</h4> ----------------------------------------------------------------------- Summary of changes: .../access/joran/action/ConfigurationAction.java | 3 + .../classic/joran/action/ConfigurationAction.java | 6 +- .../java/ch/qos/logback/core/CoreConstants.java | 7 +++ .../java/ch/qos/logback/core/util/ContextUtil.java | 42 ++++++++++++++++++++ .../java/ch/qos/logback/core/util/SystemInfo.java | 4 +- .../src/site/pages/manual/configuration.html | 3 +- 6 files changed, 60 insertions(+), 5 deletions(-) create mode 100644 logback-core/src/main/java/ch/qos/logback/core/util/ContextUtil.java hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

MessageFormatter
by Ruediger zu Dohna 22 Jan '10

22 Jan '10

Hi! Logback has two levels of formatting: One for the complete log entry and one for the log message itself. While it's flexible with the first, it's restrictive with the second, as the MessageFormatter class is right now a static-methods-only singleton. By making it an interface with a default implementation, one could reconfigure a Layout to use a different Formatter with other features. We'd like to have a message formatter that: 1. Appends all arguments that don't have a formatting anchor ("{}"). 2. Configurably allow special formatting of arguments of some class. The workaround we are living with now is to use mainly a copy of the current MessageFormatter class. Before I file an JIRA entry and maybe even provide a patch, I'd like to know what others think. Regards Rü

5 9

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-10-g3b58f83
by git-noreply＠pixie.qos.ch 16 Jan '10

16 Jan '10

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 3b58f83f64a4b00f17505f112cd5831232ae4a8b (commit) from 0f49f9823c552f09a461c0d8cad04a3c07b37e75 (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=3b58f83f64a4b00f17505f11… http://github.com/ceki/logback/commit/3b58f83f64a4b00f17505f112cd5831232ae4… commit 3b58f83f64a4b00f17505f112cd5831232ae4a8b Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Jan 16 21:39:40 2010 +0100 added quotes I like in 2 chapters of the manual diff --git a/logback-site/src/site/pages/manual/migrationFromLog4j.html b/logback-site/src/site/pages/manual/migrationFromLog4j.html index 5c2c349..a0b7059 100644 --- a/logback-site/src/site/pages/manual/migrationFromLog4j.html +++ b/logback-site/src/site/pages/manual/migrationFromLog4j.html @@ -25,6 +25,12 @@ <h2>Migration from log4j</h2> + <div class="quote"> + <p><em>The more things change, the more they remain the + same. </em></p> + + <p>—ALPHONSE KARR, <em>Les Guêpes</em></p> + </div> <p>This chapter deals with the topic of migrating custom log4j components such as appenders or layouts to logback-classic. diff --git a/logback-site/src/site/pages/manual/onJoran.html b/logback-site/src/site/pages/manual/onJoran.html index 8027707..8d70b3b 100644 --- a/logback-site/src/site/pages/manual/onJoran.html +++ b/logback-site/src/site/pages/manual/onJoran.html @@ -25,6 +25,13 @@ <h2>Joran in your own applications</h2> + <div class="quote"> + <p><em>The answer, my friend, is blowin' in the wind, The answer + is blowin' in the wind.</em></p> + + <p>—BOB DYLAN, <em>The Freewheelin' Bob Dylan</em></p> + </div> + <p>As apparent in previous chapters, logback relies on Joran, a mature, flexible and powerful configuration framework. Many of the capabilities offered by logback modules are only possible on ----------------------------------------------------------------------- Summary of changes: .../src/site/pages/manual/migrationFromLog4j.html | 6 ++++++ logback-site/src/site/pages/manual/onJoran.html | 7 +++++++ 2 files changed, 13 insertions(+), 0 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Commented: (LBCORE-18) classloader for loading autoConfig configuration resource
by Darryl Smith (JIRA) 12 Jan '10

12 Jan '10

[ http://jira.qos.ch/browse/LBCORE-18?page=com.atlassian.jira.plugin.system.i… ] Darryl Smith commented on LBCORE-18: ------------------------------------ I think logback should fallback to TCCL, ran into some problems with glassfish v3 http://forums.java.net/jive/message.jspa?messageID=379078#379078 > classloader for loading autoConfig configuration resource > --------------------------------------------------------- > > Key: LBCORE-18 > URL: http://jira.qos.ch/browse/LBCORE-18 > Project: logback-core > Issue Type: Bug > Components: Other > Affects Versions: unspecified > Environment: Operating System: Windows > Platform: PC > Reporter: Filip Jirsák > Assignee: Logback dev list > Priority: Blocker > Attachments: classloader.patch > > > ContextInitializer.autoConfig(LoggerContext) uses current thread context ClassLoader (TCL) nowadays - it calls Thread.currentThread().getContextClassLoader(). Sometimes this classloader has no access to logback classes - for example TCL is parent of classloader, which loaded current class, in oc4j (Oracle J2EE container) at the time of starting servlet container. So logback-*.jar are in WEB-INF/lib directory, but TCL has no access to these jars and to files in WEB-INF/classes. > I think ContextInitializer.autoConfig(LoggerContext) should try this.getClass().getClassLoader() first and only if it fails it should use Thread.currentThread().getContextClassLoader(). -- 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

1 0

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-9-g0f49f98
by git-noreply＠pixie.qos.ch 06 Jan '10

06 Jan '10

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 0f49f9823c552f09a461c0d8cad04a3c07b37e75 (commit) from 75e4494c35db38d4af92ced77109deb1407ec713 (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=0f49f9823c552f09a461c0d8… http://github.com/ceki/logback/commit/0f49f9823c552f09a461c0d8cad04a3c07b37… commit 0f49f9823c552f09a461c0d8cad04a3c07b37e75 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Jan 7 00:10:01 2010 +0100 Minor changes related to OnMarkerEvaluator diff --git a/logback-examples/src/main/java/chapter4/mail/mailWithMarker.xml b/logback-examples/src/main/java/chapter4/mail/mailWithMarker.xml index 4277f37..c1c7127 100644 --- a/logback-examples/src/main/java/chapter4/mail/mailWithMarker.xml +++ b/logback-examples/src/main/java/chapter4/mail/mailWithMarker.xml @@ -4,6 +4,8 @@ <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>NOTIFY_ADMIN</marker> +  + <marker>ANOTHER_MARKER</marker> </evaluator> <BufferSize>1050</BufferSize> <SMTPHost>${smtpHost}</SMTPHost> diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 48c55d2..9a273c6 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -2299,8 +2299,12 @@ Context ctx = new InitialContext(env);</pre> </p> --> - <p>You can find more information on event evaluators further - down this document. + <p>Logback ships with several other evaluators, namely <a + href="../xref/ch/qos/logback/classic/boolex/OnMarkerEvaluator.html"><code>OnMarkerEvaluator</code></a> + (discussed below) and a powerful evaluator called <a + href="../xref/ch/qos/logback/classic/boolex/JaninoEventEvaluator.html"><code>JaninoEventEvaluator</code></a>, + discussed in <a href="filters.html#evalutatorFilter">another + chapter</a>. </p> </td> @@ -2529,19 +2533,19 @@ public class CounterBasedEvaluator extends ContextAwareBase implements EventEval } }</pre> - <p> - Note that this implementation extends <code>ContextAwareBase</code> and - implements <code>EventEvaluator</code>. This allows the user to concentrate - on the core functions of her <code>EventEvaluator</code> and let the base class - provide the common functionality. + <p>Note that this class extends <code>ContextAwareBase</code> and + implements <code>EventEvaluator</code>. This allows the user to + concentrate on the core functions of her + <code>EventEvaluator</code> and let the base class provide the + common functionality. </p> - <p> - Setting the <span class="option">EventEvaluator</span> option of - <code>SMTPAppender</code> instructs it to use a custom evaluator. - The next configuration file attaches a <code>SMTPAppender</code> to the root logger. - This appender has a buffer size of 2048 and uses a <code>CounterBasedEvaluator</code> instance - as its event evaluator. + <p>Setting the <span class="option">Evaluator</span> option of + <code>SMTPAppender</code> instructs it to use a custom evaluator. + The next configuration file attaches a <code>SMTPAppender</code> + to the root logger. This appender has a buffer size of 2048 and + uses a <code>CounterBasedEvaluator</code> instance as its event + evaluator. </p> <em>Example 4.<span class="autoEx"/>: <code>SMTPAppender</code> with custom @@ -2584,10 +2588,14 @@ public class CounterBasedEvaluator extends ContextAwareBase implements EventEval </p> <pre class="prettyprint source">Marker notifyAdminMarker = MarkerFactory.getMarker("NOTIFY_ADMIN"); -logger.error(notifyAdminMarker, +logger.error(<b>notifyAdminMarker</b>, "This is a serious an error requiring the admin's attention", new Exception("Just testing"));</pre> - + + <p>The next configuration file will cause outgoing emails to be + sent only in presensce of events bearing the NOTIFY_ADMIN or the + TRANSACTION_FAILURE marker. + </p> <em>Example 4.<span class="autoEx"/>: <code>SMTPAppender</code> with <code>OnMarkerEvaluator</code> (logback-examples/src/main/java/chapter4/mail/mailWithMarker.xml)</em> @@ -2596,6 +2604,8 @@ logger.error(notifyAdminMarker, <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <b><evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>NOTIFY_ADMIN</marker> +  + <marker>TRANSACTION_FAILURE</marker> </evaluator></b> <BufferSize>1050</BufferSize> <SMTPHost>${smtpHost}</SMTPHost> @@ -2610,6 +2620,11 @@ logger.error(notifyAdminMarker, </root> </configuration></pre> + <p>Give it a whirl with the following command:</p> + + <pre class="source">java -Dfrom=source(a)xyz.com -Dto=recipient(a)xyz.com -DsmtpHost=some_smtp_host \ + chapter4.mail.Marked_EMail src/main/java/chapter4/mail/mailWithMarker.xml</pre> + <h3><a name="smtpAuthentication" diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 94525d4..b11639d 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -28,6 +28,17 @@ <hr width="80%" align="center" /> + <h3>January 2010 - Release of version 0.9.19</h3> + + <p>Added <a + href="manual/appenders.html#OnMarkerEvaluator">OnMarkerEvaluator</a> + which evaluates to true in the presence of user-specified + markers. When used with <code>SMTPAppender</code>, it can trigger + an outgoing email message when an event matches user-specified + marker.</p> + + <hr width="80%" align="center" /> + <h3>3rd of December 2009 - Release of version 0.9.18</h3> <p>After a very long investigation resulting in somewhat a better ----------------------------------------------------------------------- Summary of changes: .../src/main/java/chapter4/mail/mailWithMarker.xml | 2 + logback-site/src/site/pages/manual/appenders.html | 45 +++++++++++++------- logback-site/src/site/pages/news.html | 11 +++++ 3 files changed, 43 insertions(+), 15 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0