September 2010 - logback-dev

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.24-14-g487c887
by git-noreply＠pixie.qos.ch 15 Sep '10

15 Sep '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 487c8871c3c728dbe7be248a0c81c99d3e4e8fad (commit) from bf373eb4461e45e92f26f417bc63cdb1dd2b60e8 (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=487c8871c3c728dbe7be248a… http://github.com/ceki/logback/commit/487c8871c3c728dbe7be248a0c81c99d3e4e8… commit 487c8871c3c728dbe7be248a0c81c99d3e4e8fad Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Sep 15 22:42:10 2010 +0200 typo fix diff --git a/logback-site/src/site/pages/manual/layouts.html b/logback-site/src/site/pages/manual/layouts.html index ccee3c3..ee5c81b 100644 --- a/logback-site/src/site/pages/manual/layouts.html +++ b/logback-site/src/site/pages/manual/layouts.html @@ -1762,7 +1762,7 @@ public class MySampleConverter extends ClassicConverter { <pre class="prettyprint source"><layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%relative...%msg</pattern> - <cssBuilder class="ch.qos.logback.core.html.UrlCssBuilder"> + <cssBuilder class="ch.qos.logback.classic.html.UrlCssBuilder">  <url>http://...</url> </cssBuilder> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/layouts.html | 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. v_0.9.24-13-gbf373eb
by git-noreply＠pixie.qos.ch 10 Sep '10

10 Sep '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 bf373eb4461e45e92f26f417bc63cdb1dd2b60e8 (commit) from 91b5a954630b626d18bb9cf131490814e63a999d (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=bf373eb4461e45e92f26f417… http://github.com/ceki/logback/commit/bf373eb4461e45e92f26f417bc63cdb1dd2b6… commit bf373eb4461e45e92f26f417bc63cdb1dd2b60e8 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Sep 2 21:33:54 2010 +0200 Use the correct value for TRACE_INTEGER. This value is used currently used only by JaninoEvaluator. diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/Level.java b/logback-classic/src/main/java/ch/qos/logback/classic/Level.java index 7a3798e..0cf3246 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/Level.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/Level.java @@ -37,7 +37,7 @@ public final class Level implements java.io.Serializable { public static final Integer WARN_INTEGER = new Integer(WARN_INT); public static final Integer INFO_INTEGER = new Integer(INFO_INT); public static final Integer DEBUG_INTEGER = new Integer(DEBUG_INT); - public static final Integer TRACE_INTEGER = new Integer(DEBUG_INT); + public static final Integer TRACE_INTEGER = new Integer(TRACE_INT); public static final Integer ALL_INTEGER = new Integer(ALL_INT); /** ----------------------------------------------------------------------- Summary of changes: .../main/java/ch/qos/logback/classic/Level.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Moved: (LBACCESS-15) TeeFilter should be disabled in productions systems
by Ceki Gulcu (JIRA) 03 Sep '10

03 Sep '10

[ http://jira.qos.ch/browse/LBACCESS-15?page=com.atlassian.jira.plugin.system… ] Ceki Gulcu moved LBAUDIT-1 to LBACCESS-15: ------------------------------------------ Project: logback-access (was: logback-audit) Key: LBACCESS-15 (was: LBAUDIT-1) > TeeFilter should be disabled in productions systems > --------------------------------------------------- > > Key: LBACCESS-15 > URL: http://jira.qos.ch/browse/LBACCESS-15 > Project: logback-access > Issue Type: New Feature > Reporter: Ceki Gulcu > Assignee: Logback dev list > > Given that TeeFilter is part of web.xml it transpires into production which can be highly undesirable. > Example: > <filter> > <filter-name>TeeFilter</filter-name> > <filter-class>ch.qos.logback.access.servlet.TeeFilter</filter-class> > <init-param> > <param-name>ignoreOnHost</param-name> > <param-value>prodHost0, prodHost1</param-value> > </init-param> > </filter> -- 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

Logback Refactoring Ideas
by Gunnar Wagenknecht 02 Sep '10

02 Sep '10

Greetings Logback developers, I'm regularly packaging Logback OSGi bundles for Eclipse Orbit. The other day I was wondering if the current core vs. classic split of Logback is really useful for people, i.e. is anybody out there using _just_ Logback core without any of the classic pieces? For example, PatternLayout is classic but the file appenders are in core. Isn't PatternLayout an essential logging element? Also, when an issue in the XML/Groofvy configuration implementation is detected, a full new release of core+classic is required. Wouldn't it be better if the parts could evolve independent? Thus, I was thinking of a more fine grained split based on functional units. For example like this: -> Logback Logging Essentials All the essential logging related stuff form core+classic (logger, levels, (turbo) filters, console appender, encoders, layouts, basic configurator) -> Logback SLF4J Logger The native SLF4J logger. -> Logback XML/Groovy Configuration Pack The advanced configuration functionality based on Joran for XML + Groovy. -> Logback File Logging Extension Pack File appenders -> Logback Web Extension Pack Servlet integration, HTML appenders, etc. -> Logback Enterprise Extension Pack Advanced appenders (JMS, Database), JNDI stuff, etc. There could be other extension packs as well. The challenge IMHO is to collect all the essential things together for having a really small Logback package that contains only the minimum required for logging (to console and to files). Maybe the file logging package can be part of the essential package. Anyway, another important point is that the packages are released independently, i.e. get their own version. Thus, when an issue in the XML/Groovy configuration package is detected, no new release of the essential pack is necessary. There can still be joint releases of all packs together (for example, to have a better brand recognition) - the "Logback 1.2" release. But in this case, Logback 1.2 means essentials 1.0.4, slf4j-logger 1.0.1, configs 1.2.0, file logging 1.1.24, etc. Thoughts? -Gunnar -- Gunnar Wagenknecht gunnar(a)wagenknecht.org http://wagenknecht.org/

3 3