July 2010 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCORE-159) AppenderBase and UnsynchronizedAppenderBsae do not allow exceptions to percolate to the application
by Ralph Goers (JIRA) 13 Oct '10

13 Oct '10

AppenderBase and UnsynchronizedAppenderBsae do not allow exceptions to percolate to the application --------------------------------------------------------------------------------------------------- Key: LBCORE-159 URL: http://jira.qos.ch/browse/LBCORE-159 Project: logback-core Issue Type: Improvement Components: Appender Affects Versions: 0.9.24 Environment: All Reporter: Ralph Goers Assignee: Logback dev list When logging some events the application needs to be informed that the publishing of the event failed. Currently, AppenderBase and UnsynchronizedAppenderBase catch and handle all exceptions making it impossible to use any of the out-of-the box Logback appenders in these situations. This is particularly important when performing auditing and sending the events to a database, JMS queue, socket, etc. as the application would want to fail the current operation if it cannot be audited. -- 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 10

[JIRA] Created: (LBCORE-117) Supply an appender that collects N events on all levels and dumps them to the output when an ERROR is logged
by Aaron Digulla (JIRA) 04 Oct '10

04 Oct '10

Supply an appender that collects N events on all levels and dumps them to the output when an ERROR is logged ------------------------------------------------------------------------------------------------------------ Key: LBCORE-117 URL: http://jira.qos.ch/browse/LBCORE-117 Project: logback-core Issue Type: New Feature Components: Appender Reporter: Aaron Digulla Assignee: Logback dev list For many applications, it's not necessary to log at the levels DEBUG and TRACE all the time. In fact, we usually only do this to be able to debug ERROR events. It would be great if there was an appender that would only collect a configurable number of events internally until a message of level ERROR or above is logged. At this time, the appender should dump it's internal state to the log and reset the internal state. -- 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

[JIRA] Created: (LBCLASSIC-211) Logback fails to configure in OSGI container, when multiple configurations found
by David Riseley (JIRA) 15 Aug '10

15 Aug '10

Logback fails to configure in OSGI container, when multiple configurations found -------------------------------------------------------------------------------- Key: LBCLASSIC-211 URL: http://jira.qos.ch/browse/LBCLASSIC-211 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.20 Environment: Apache felix OSGI container, profiling with JProbe. Sun JDK 1.6.0_17 Reporter: David Riseley Assignee: Logback dev list Priority: Minor When we attempt to profile our application, which runs in an Apache Felix OSGI container, using JProbe the Logback configuration fails with the following exception: Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.IllegalArgumentException: name at sun.misc.URLClassPath$Loader.findResource(URLClassPath.java:458) at sun.misc.URLClassPath$1.next(URLClassPath.java:195) at sun.misc.URLClassPath$1.hasMoreElements(URLClassPath.java:205) at java.net.URLClassLoader$3$1.run(URLClassLoader.java:393) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader$3.next(URLClassLoader.java:390) at java.net.URLClassLoader$3.hasMoreElements(URLClassLoader.java:415) at sun.misc.CompoundEnumeration.next(CompoundEnumeration.java:27) at sun.misc.CompoundEnumeration.hasMoreElements(CompoundEnumeration.java:36) at sun.misc.CompoundEnumeration.next(CompoundEnumeration.java:27) at sun.misc.CompoundEnumeration.hasMoreElements(CompoundEnumeration.java:36) at ch.qos.logback.core.util.Loader.getResourceOccurenceCount(Loader.java:58) at ch.qos.logback.classic.util.ContextInitializer.multiplicityWarning(ContextInitializer.java:131) at ch.qos.logback.classic.util.ContextInitializer.statusOnResourceSearch(ContextInitializer.java:154) at ch.qos.logback.classic.util.ContextInitializer.findConfigFileURLFromSystemProperties(ContextInitializer.java:88) at ch.qos.logback.classic.util.ContextInitializer.findURLOfDefaultConfigurationFile(ContextInitializer.java:97) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:119) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:83) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:54) 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 org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:261) at com.example.csp.gui.interfaces.logger.ABCDGUILoggerImpl.getLogger(ABCDGUILoggerImpl.java:74) at com.example.csp.gui.interfaces.logger.ABCDGUILoggerFactory.getLogger(ABCDGUILoggerFactory.java:51) at com.example.csp.gui.kernel.util.ABCDGUIKernelUtil.<clinit>(ABCDGUIKernelUtil.java:61) at com.example.csp.gui.kernel.context.impl.ABCDGUIKernelContextImpl.setAppBaseBundleInContext(ABCDGUIKernelContextImpl.java:207) at com.example.csp.gui.kernel.context.impl.ABCDGUIKernelContextImpl.init(ABCDGUIKernelContextImpl.java:93) at com.example.csp.gui.kernel.context.impl.ABCDGUIKernelContextImpl.<init>(ABCDGUIKernelContextImpl.java:58) at com.example.csp.gui.kernel.activator.impl.KernelActivatorImpl.start(KernelActivatorImpl.java:101) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589) at org.apache.felix.framework.Felix.startBundle(Felix.java:1458) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263) at java.lang.Thread.run(Thread.java:619) SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/C:/ngawab/wab_code/code/source/wnb-common-bundles/wnb-common-client/startup-2.0.3/csp-gui-thickclient-bootstrap-2.0.3-all.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [bundle://4.0:1/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. After which we get no logging at all. I appreciate that this will be difficult to reproduce , and I think may be related to the "bundle://" URL format not being recognised, so I had a look at the code in ch.qos.logback.classic.util.ContextInitializer.multiplicityWarning() Currently it catches an IOExeception when calling Loader.getResourceOccurenceCount(), however from the stack trace this can also throw an. IllegalArgumentException So could : try { urlList = Loader.getResourceOccurenceCount(resourceName, classLoader); } catch (IOException e) { sm.add(new ErrorStatus("Failed to get url list for resource [" + resourceName + "]", loggerContext, e)); } Become: try { urlList = Loader.getResourceOccurenceCount(resourceName, classLoader); } catch (Exception e) { sm.add(new ErrorStatus("Failed to get url list for resource [" + resourceName + "]", loggerContext, e)); } I did try this in our environment , and the logging did get successfully configured after this change ( although it wasn't pretty.... :-> ) -- 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

3 5

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.24-6-g10b6686
by git-noreply＠pixie.qos.ch 30 Jul '10

30 Jul '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 10b6686ab92a53f860b14953ce8493d5c3534a46 (commit) from 15b5239b5d583a86877b79e77336729317cf2dc0 (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=10b6686ab92a53f860b14953… http://github.com/ceki/logback/commit/10b6686ab92a53f860b14953ce8493d5c3534… commit 10b6686ab92a53f860b14953ce8493d5c3534a46 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Jul 30 14:18:14 2010 +0200 - minor edits in configuration.html - correct tag names in codes.html#layoutInsteadOfEncoder diff --git a/logback-site/src/site/pages/codes.html b/logback-site/src/site/pages/codes.html index 27607c5..8a936c8 100644 --- a/logback-site/src/site/pages/codes.html +++ b/logback-site/src/site/pages/codes.html @@ -87,7 +87,7 @@ ... <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>%msg%n</pattern> - </encode> + </encoder> </appender> </pre> <p class="green bold">or the shorter equivalent (GOOD)</p> @@ -99,7 +99,7 @@ ch.qos.logback.classic.encoder.PatternLayoutEncoder by default --> <encoder> <pattern>%msg%n</pattern> - </encode> + </encoder> </appender> </pre> diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 533ebef..1a28588 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -378,8 +378,9 @@ public class Foo { printed. </p> - <h3>Specifying the location of the default configuration file as a - system property</h3> + <h3><a name="configFileProperty" + href="#configFileProperty">Specifying the location of the default + configuration file as a system property</a></h3> <p>If you wish, you can specify the location of the default configuration file with a system property named @@ -469,7 +470,8 @@ public class Foo { - <h3>Invoking <code>JoranConfigurator</code> directly</h3> + <h3><a name="joranDirectly" href="#joranDirectly">Invoking + <code>JoranConfigurator</code> directly</a></h3> <p>Logback relies on a configuration library called Joran which is part of logback-core. Logback's default configuration mechanism ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/codes.html | 4 ++-- .../src/site/pages/manual/configuration.html | 8 +++++--- 2 files changed, 7 insertions(+), 5 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBACCESS-13) Update logback-access to jetty 7
by Ceki Gulcu (JIRA) 23 Jul '10

23 Jul '10

Update logback-access to jetty 7 -------------------------------- Key: LBACCESS-13 URL: http://jira.qos.ch/browse/LBACCESS-13 Project: logback-access Issue Type: Task Reporter: Ceki Gulcu Assignee: Logback dev list http://www.qos.ch/pipermail/logback-user/2010-July/001698.html -- 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 2

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.24-5-g15b5239
by git-noreply＠pixie.qos.ch 20 Jul '10

20 Jul '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 15b5239b5d583a86877b79e77336729317cf2dc0 (commit) from b9057d8058cac20399f313237c232221a6aee384 (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=15b5239b5d583a86877b79e7… http://github.com/ceki/logback/commit/15b5239b5d583a86877b79e77336729317cf2… commit 15b5239b5d583a86877b79e77336729317cf2dc0 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Jul 20 22:35:39 2010 +0200 Minor edit (fix supplied by Mark Vedder) diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 4a9b92c..de7769a 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -454,8 +454,8 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl </p> <p>Prudent mode effectively serializes IO operations between - all JVMs writing to the same file. Thus, as he number of JVMs - competing to access the file increases so will the delay + all JVMs writing to the same file. Thus, as the number of + JVMs competing to access the file increases so will the delay incurred by each I/O operation. As long as the <em>total</em> number of I/O operations is in the order of 20 log requests per second, the impact on performance should be ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 4 ++-- 1 files changed, 2 insertions(+), 2 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-4-gb9057d8
by git-noreply＠pixie.qos.ch 15 Jul '10

15 Jul '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 b9057d8058cac20399f313237c232221a6aee384 (commit) from ce5cd47ea3eeeae06e82f6e729417291edf024de (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=b9057d8058cac20399f31323… http://github.com/ceki/logback/commit/b9057d8058cac20399f313237c232221a6aee… commit b9057d8058cac20399f313237c232221a6aee384 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Jul 15 13:01:55 2010 +0200 Minor edit diff --git a/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy b/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy index 162df73..9635eda 100644 --- a/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy +++ b/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy @@ -48,7 +48,7 @@ class GafferConfigurator { dslScript.metaClass.mixin(ConfigurationDelegate) dslScript.setContext(context) - dslScript.metaClass.getDeclaredOrigin = { println "getDeclaredOrigin"; dslScript } + dslScript.metaClass.getDeclaredOrigin = { dslScript } // metaClass.statusListener = configurationDelegate.&statusListener // dslScript.metaClass.scan = configurationDelegate.&scan // dslScript.metaClass.appender = configurationDelegate.&appender ----------------------------------------------------------------------- Summary of changes: .../classic/gaffer/GafferConfigurator.groovy | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBSITE-41) Eclipse console plug-in warning is out dated
by Jason Tholstrup (JIRA) 08 Jul '10

08 Jul '10

Eclipse console plug-in warning is out dated -------------------------------------------- Key: LBSITE-41 URL: http://jira.qos.ch/browse/LBSITE-41 Project: logback-site Issue Type: Bug Components: Documentation Reporter: Jason Tholstrup Assignee: Logback dev list Priority: Minor On the download page http://logback.qos.ch/download.html there is a reference to the Eclipse plug-in. Unfortunately, the console plugin is somewhat outdated. It expects logback version 0.9.9. It will be upgraded in the coming weeks. But when you click on it, it is clearly at version 1.1.0. This should probably be updated so as to avoid confusion. -- 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. v_0.9.24-3-gce5cd47
by git-noreply＠pixie.qos.ch 08 Jul '10

08 Jul '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 ce5cd47ea3eeeae06e82f6e729417291edf024de (commit) from 11350106a9af1ada33bfb04ba3a3b64d9c9bb6cb (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=ce5cd47ea3eeeae06e82f6e7… http://github.com/ceki/logback/commit/ce5cd47ea3eeeae06e82f6e729417291edf02… commit ce5cd47ea3eeeae06e82f6e729417291edf024de Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Jul 8 16:08:46 2010 +0200 - added link to an article by Cyrille Le Clerc - minor editing in /reasonsToSwitch diff --git a/logback-site/src/site/pages/documentation.html b/logback-site/src/site/pages/documentation.html index 9b589d2..f965c74 100644 --- a/logback-site/src/site/pages/documentation.html +++ b/logback-site/src/site/pages/documentation.html @@ -113,6 +113,14 @@ href="http://www.insideit.fr/post/2009/11/23/SLF4J-LOGBack">SLF4J & LOGBack : simplifiez-vous les logs</a> by Ludovic Meurillon </li> + + + <li><a + href="http://blog.xebia.fr/2010/07/07/java-en-production-les-fichiers-de-logs/">Java + en Production - Les fichiers de logs</a> by Cyrille Le Clerc + </li> + + </ul> diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html index 454ca22..cdb0b78 100644 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -23,7 +23,8 @@ <p>Here is a non-exhaustive list of reasons for switching to logback from log4j. Keep in mind that logback is conceptually very - similar to log4j. If you are already familiar with log4j, you will + similar to log4j as both projects were founded by Ceki + Gülcü. If you are already familiar with log4j, you will quickly feel at home using logback.</p> <h3><a name="fasterImpl" href="#fasterImpl">Faster implementation</a></h3> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/documentation.html | 8 ++++++++ logback-site/src/site/pages/reasonsToSwitch.html | 3 ++- 2 files changed, 10 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-2-g1135010
by git-noreply＠pixie.qos.ch 08 Jul '10

08 Jul '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 11350106a9af1ada33bfb04ba3a3b64d9c9bb6cb (commit) from 595d725652ecbf30f985a9f3518bc82a3bfede57 (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=11350106a9af1ada33bfb04b… http://github.com/ceki/logback/commit/11350106a9af1ada33bfb04ba3a3b64d9c9bb… commit 11350106a9af1ada33bfb04ba3a3b64d9c9bb6cb Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Jul 8 08:28:40 2010 +0200 - minor editing diff --git a/logback-site/src/site/pages/manual/groovy.html b/logback-site/src/site/pages/manual/groovy.html index f234f22..064dcb9 100644 --- a/logback-site/src/site/pages/manual/groovy.html +++ b/logback-site/src/site/pages/manual/groovy.html @@ -84,8 +84,9 @@ <p>Given that <em>logback.groovy</em> files are groovy programs with minimal logback-specific extensins, <em>all</em> the usual groovy constructs such as class imports, variable definitions, - evaluation of ${..} expressions in a string (GStrings), if-else - statements are all avaiable in <em>logback.groovy</em> files.</p> + evaluation of ${..} expressions contained in strings + (GStrings), if-else statements are all avaiable in + <em>logback.groovy</em> files.</p> <h2>Extensions specific to <em>logback.groovy</em></h2> @@ -182,7 +183,9 @@ logger("com.foo", DEBUG, ["CONSOLE"], false)</pre> a method named after the property and passing that method the class to instantiate as an argument. This convention can be applied recursively to configure properties as well as - sub-components of any appender sub-component. </p> + sub-components of any appender sub-component. This approach is at + the heart of <em>logback.groovy</em> scripts and is probably the + only convention that needs learning.</p> <p>For example, the following script instantiates a <code>FileAppender</code> named "FILE", setting its <span @@ -322,10 +325,11 @@ root(DEBUG, ["STDOUT"])</pre> <p>The <em>logback.groovy</em> is an internal DSL meaning that its contents are executed as a groovy script. Thus, all the usual groovy constructs such as class imports, GString, variable - definitions, evaluation of ${..} expressions in a string - (GStrings), if-else statements are all avaiable in logback.groovy - files. In the following discussion, we will present typical uses - of these groovy constructs in <em>logback.groovy</em> files. + definitions, evaluation of ${..} expressions contained + within strings (GStrings), if-else statements are all avaiable in + logback.groovy files. In the following discussion, we will present + typical uses of these groovy constructs in <em>logback.groovy</em> + files. </p> @@ -357,8 +361,8 @@ root(DEBUG, ["FILE"])</pre> <h3>Printing on the console</h3> - <p>You can invoke the println method to print on the console. Here - is an example.</p> + <p>You can invoke Groovy's <code>println</code> method to print on + the console. Here is an example.</p> <pre class="prettyprint source">import ch.qos.logback.classic.encoder.PatternLayoutEncoder import ch.qos.logback.core.FileAppender @@ -423,13 +427,14 @@ appender("STDOUT", ConsoleAppender) { <h3>Everything is context aware with a reference to the current context</h3> - <p>The execution of the logback.grooy script is done within a scope - of a <a + <p>The execution of the <em>logback.grooy</em> script is done + within a scope of a <a href="../xref/ch/qos/logback/core/spi/ContextAware.html">ContextAware</a> object. Thus, the current context is always accessible using the - '<code>context</code>' variable and you can add status messages - using <code>addInfo</code>(), <code>addWarn</code> and addError - methods.</p> + '<code>context</code>' variable and you can invoke + <code>addInfo</code>(), <code>addWarn</code>() and + <code>addError</code>() methods to send status messages to the + context's <code>StatusManager</code>.</p> <pre class="prettyprint source">import ch.qos.logback.classic.encoder.PatternLayoutEncoder import ch.qos.logback.core.FileAppender @@ -463,9 +468,9 @@ root(DEBUG, ["FILE"])</pre> <h3>Conditional configuration</h3> <p>Given that Groovy is a fully-fledged programming language, - conditional statements allow for a single logback.groovy file to - adapt to various environments such as development, testing or - production.</p> + conditional statements allow for a single <em>logback.groovy</em> + file to adapt to various environments such as development, testing + or production.</p> <p>In the next script, a console appender is activated on hosts other than pixie or orion, our production machines. Note that the diff --git a/logback-site/src/site/pages/templates/footer.js b/logback-site/src/site/pages/templates/footer.js index fc60fd3..630bee2 100644 --- a/logback-site/src/site/pages/templates/footer.js +++ b/logback-site/src/site/pages/templates/footer.js @@ -1,10 +1,6 @@ document.write('<table class="footer">') - - -document.write('</tr>') - document.write('<tr>') document.write(' <td>') ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/groovy.html | 39 +++++++++++++---------- logback-site/src/site/pages/templates/footer.js | 4 -- 2 files changed, 22 insertions(+), 21 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0