September 2010 - logback-dev

[JIRA] Created: (LBCORE-154) Use of default values in appender-refs
by David Harrigan (JIRA) 13 Oct '10

13 Oct '10

Use of default values in appender-refs -------------------------------------- Key: LBCORE-154 URL: http://jira.qos.ch/browse/LBCORE-154 Project: logback-core Issue Type: Improvement Components: Appender Environment: All Reporter: David Harrigan Assignee: Logback dev list This is referenced also here: http://old.nabble.com/Appender-Ref-Default-Value-to28605941.html Please can we have the ability to specify default values for appender-refs. I have a use case where we need to "bake-in" the appender during build-time. I can do this at the moment for logger level by bringing in a property file (called override.properties) that can reset the logging level (which is dependent on the deployment environment and other factors). Here is a little example: <property resource="override.properties" /> <logger name="bar.foo" level="${bar.foo.log.level:-info}" additivity="false"> <appender-ref ref="console"/> </logger> The bar.foo.log.level is defined in the override.properties file. The correct file gets inserted for each build type. I would like to do the following as well: <logger name="bar.foo" level="${bar.foo.log.level:-info}" additivity="false"> <appender-ref ref="${bar.foo.log.appender:-console}"/> </logger> So that I can tell the override where to log to (console for development or log file, or smtp, or jms, or db for other environments). This would be so neato if implemented :-) Thank you. -=david=- -- 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 8

[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

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

30 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 090b95566ecbae1a3321bed43b1d9c15dcac32e8 (commit) from b100fbfa7db3cd43d4551bd70bb523a5c7543311 (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=090b95566ecbae1a3321bed4… http://github.com/ceki/logback/commit/090b95566ecbae1a3321bed43b1d9c15dcac3… commit 090b95566ecbae1a3321bed43b1d9c15dcac32e8 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Sep 30 22:02:23 2010 +0200 typo fix diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index fe45f69..0755721 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -2142,7 +2142,7 @@ Context ctx = new InitialContext(env);</pre> The <a href="../xref/ch/qos/logback/classic/net/SMTPAppender.html"><code>SMTPAppender</code></a> accumulates logging events in one or more fixed-size buffers and - sends the contents of the appropriate bufferer in an email after a + sends the contents of the appropriate buffer in an email after a user-specified event occurs. By default, the email transmission is triggered by a logging event of level ERROR or higher. Moreover, by default, a single buffer is used for all events. ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.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-19-gb100fbf
by git-noreply＠pixie.qos.ch 30 Sep '10

30 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 b100fbfa7db3cd43d4551bd70bb523a5c7543311 (commit) from 74915053db48b5e803816f8d39237cd85293273f (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=b100fbfa7db3cd43d4551bd7… http://github.com/ceki/logback/commit/b100fbfa7db3cd43d4551bd70bb523a5c7543… commit b100fbfa7db3cd43d4551bd70bb523a5c7543311 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Sep 30 21:58:31 2010 +0200 - Many editorial fixes submitted by Dan Lantz. diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 6196232..fe45f69 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -65,7 +65,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl }</pre> Most of the methods in the <code>Appender</code> interface are - made of setter and getter methods. A notable exception is the + setters and getters. A notable exception is the <code>doAppend()</code> method taking an object instance of type E as its only parameter. The actual type of E would vary depending on the logback module. Within the @@ -300,8 +300,8 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl <code>ConsoleAppender</code></a>, as the name indicates, appends on the console, or more precisely on System.out or System.err, the former being the default - target. <code>ConsoleAppender</code> formats events with the hellp - of an encoder specified by the user. Encoders will be discussed in a + target. <code>ConsoleAppender</code> formats events with the help of + an encoder specified by the user. Encoders will be discussed in a subsequent chapter. Both System.out and System.err are of type <code>java.io.PrintStream</code>. Consequently, they are wrapped inside an <code>OutputStreamWriter</code> which buffers @@ -586,8 +586,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl below</a>) will determine if and exactly when rollover occurs. Thus, <code>RollingPolicy</code> is responsible for the what and <code>TriggeringPolicy</code> is responsible for - the when. <code>RollingPolicy</code> is described - + the when. To be of any use, a <code>RollingFileAppender</code> must have both a <code>RollingPolicy</code> and a @@ -906,9 +905,10 @@ public interface RollingPolicy extends LifeCycle { interfaces. - <code>TimeBasedRollingPolicy</code>'s admits two properties, the - mandatory fileNamePattern property and - the optional maxHistory property. + <code>TimeBasedRollingPolicy</code>'s configuration admits two + properties, the mandatory fileNamePattern property and the optional + maxHistory property. <table class="bodyTable"> @@ -2142,7 +2142,7 @@ Context ctx = new InitialContext(env);</pre> The <a href="../xref/ch/qos/logback/classic/net/SMTPAppender.html"><code>SMTPAppender</code></a> accumulates logging events in one or more fixed-size buffers and - sends the contents of the appropriate bugger in an email after a + sends the contents of the appropriate bufferer in an email after a user-specified event occurs. By default, the email transmission is triggered by a logging event of level ERROR or higher. Moreover, by default, a single buffer is used for all events. diff --git a/logback-site/src/site/pages/manual/architecture.html b/logback-site/src/site/pages/manual/architecture.html index 3af7059..b4a5841 100644 --- a/logback-site/src/site/pages/manual/architecture.html +++ b/logback-site/src/site/pages/manual/architecture.html @@ -745,11 +745,11 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> <h4>1. Get the filter chain decision</h4> If it exists, the <code>TurboFilter</code> chain is - invoked. Turbo filters can set a context-wide threshold, or to - filter out certain events based on information such as - <code>Marker</code>, <code>Level</code>, <code>Logger</code>, - message, or the <code>Throwable</code> that are associated with each - logging request. If the reply of the filter chain is + invoked. Turbo filters can set a context-wide threshold, or filter + out certain events based on information such as <code>Marker</code>, + <code>Level</code>, <code>Logger</code>, message, or the + <code>Throwable</code> that are associated with each logging + request. If the reply of the filter chain is <code>FilterReply.DENY</code>, then the logging request is dropped. If it is <code>FilterReply.NEUTRAL</code>, then we continue with the next step, i.e. step 2. In case the reply is @@ -880,12 +880,12 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> and 4 microseconds to format a message with 1 and 3 parameters. - Please notice that, despite the performance points that we just - discussed, inserting logging statements in tight loops or very - frequently invoked code is a lose-lose proposal and is likely to - result in degraded performance. Logging in tight loops slow down - your application even if logging is turned off, and if logging is - turned on, they will generate massive (and hence useless) output. + Please notice that, despite the performance points just + discussed, inserting logging statements in tight loops (very + frequently invoked code) is a lose-lose proposal and is likely to + result in degraded performance. Logging in tight loops will slow + down your application even if logging is turned off, and if logging + is turned on, will generate massive (and hence useless) output. <h4>2. The performance of deciding whether to log or not to log when diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 769d170..9782baf 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -218,7 +218,7 @@ public class Foo { </div> The <code>MyApp1</code> application links to logback via calls - <code>org.slf4j.LoggerFactory</code> and + to <code>org.slf4j.LoggerFactory</code> and <code>org.slf4j.Logger</code> classes, retrieve the loggers it wishes to use, and chugs on. Note that the only dependencies of the <code>Foo</code> class on logback are through @@ -527,7 +527,7 @@ public class MyApp3 { currently in effect, creates a new <code>JoranConfigurator</code>, sets the context on which it will operate, resets the logger context, and then finally asks the configurator to configure the - context using configuration file passed as parameter to the + context using the configuration file passed as a parameter to the application. Internal status data is printed in case of warnings or errors. @@ -547,7 +547,7 @@ public class MyApp3 { data associated with a logback context. To keep memory usage at reasonable levels, the default <code>StatusManager</code> implementation stores the status messages in two separate parts: - the header part and the tail part. The header part stores the fist + the header part and the tail part. The header part stores the first H status messages whereas the tail part stores the last T messages. At present time H=T=150, although these values may change in future releases. @@ -709,12 +709,12 @@ public class MyApp3 { href="#loggerElement">Configuring loggers, or the <code><logger></code> element</a></h4> - At this point should have at least some understanding of <a + At this point you should have at least some understanding of <a href="architecture.html#effectiveLevel">level inheritance</a> and the <a href="architecture.html#basic_selection">basic selection rule</a>. Otherwise, and unless you are an egyptologist, logback - configuration will be no more meaningful to you than - are hieroglyphics. + configuration will be no more meaningful to you than are + hieroglyphics. A logger is configured using the <code><logger></code> @@ -893,7 +893,7 @@ public class MyApp3 { Let us note that the <a href="architecture.html#basic_selection">basic-selection rule</a> depends on the effective level of the logger being invoked, not the - level of the logger where appenders are attached. Loback will first + level of the logger where appenders are attached. Logback will first determine whether a logging statement is enabled or not, and if enabled, it will invoke the appenders found in the logger hierarchy, regardless of their level. The configuration file @@ -976,7 +976,7 @@ public class MyApp3 { <h4><a name="configuringAppenders" href="#configuringAppenders">Configuring Appenders</a></h4> - An appenders is configured with the <code><appender></code> + An appender is configured with the <code><appender></code> element, which takes two mandatory attributes name and class. The name attribute specifies the name of the @@ -1051,7 +1051,7 @@ public class MyApp3 { </root> </configuration></pre> - This configuration scripts defines two appenders called + These configuration scripts define two appenders called FILE and STDOUT. The FILE appender logs to a file called myApp.log. The encoder for this appender is a <code>PatternLayoutEncoder</code> that outputs the date, level, @@ -1113,12 +1113,14 @@ public class MyApp3 { 14:25:36.359 [main] INFO chapters.configuration.MyApp3 - Exiting application. Notice the duplicated output. The appender named STDOUT - is attached to two loggers, to root and to chapters.configuration. Since - the root logger is the ancestor of all loggers and chapters.configuration - is the parent of chapters.configuration.MyApp3 and chapters.configuration.Foo, - logging request made with these two loggers will be output twice, - once because STDOUT is attached to chapters.configuration and - once because it is attached to root. + is attached to two loggers, to root and to + chapters.configuration. Since the root logger is the + ancestor of all loggers and chapters.configuration is the + parent of both chapters.configuration.MyApp3 and + chapters.configuration.Foo, each logging request made with + these two loggers will be output twice, once because STDOUT + is attached to chapters.configuration and once because it + is attached to root. Appender additivity is not intended as a trap for new users. It @@ -1219,10 +1221,10 @@ public class MyApp3 { <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 + earlier chapter</a>, every logger is attached to a 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 @@ -1247,8 +1249,8 @@ public class MyApp3 { </root> </configuration></pre> - This last examples illustrates naming of the logger - context. Adding the the <a + This last example illustrates naming of the logger + context. Adding the <a href="layouts.html#conversionWord">contextName conversion word</a> in layout's pattern will output the said name. @@ -1363,9 +1365,9 @@ public class MyApp3 { This configuration file contains a reference to a file named variables1.properties. The variables contained in that - file will be read defined within the context of the logback - configuration file. Here is what the variable.properties - file might look like. + file will be read and then defined within the context of the + logback configuration file. Here is what the + variable.properties file might look like. Example: Variable file @@ -1598,7 +1600,7 @@ fileName=myApp.log Under certain circumstances, you may want to make use of 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. diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index 1e10a0f..481d609 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -50,7 +50,7 @@ existing logging systems, sometimes by a wide margin. Logback also offers unique and rather useful features such as Markers, parameterized logging statements, conditional stack tracing and - powerful event filtering. These are only few examples of useful + powerful event filtering. These are only a few examples of useful features logback has to offer. For its own error reporting, logback relies on <code>Status</code> objects, which greatly facilitate troubleshooting. You may wish to rely on Status objects @@ -220,7 +220,7 @@ public class HelloWorld2 { or the class itself as a parameter.</li> <li>Use this logger instance by invoking its printing methods, - namely the debug(), info(), warn() and error(). This will + namely the debug(), info(), warn() and error() methods. This will produce logging output on the configured appenders.</li> </ol> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 18 +++--- .../src/site/pages/manual/architecture.html | 22 ++++---- .../src/site/pages/manual/configuration.html | 52 ++++++++++--------- .../src/site/pages/manual/introduction.html | 4 +- 4 files changed, 49 insertions(+), 47 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCORE-167) An exception is thrown during the web application startup.
by Pavel Mikhalchuk (JIRA) 17 Sep '10

17 Sep '10

An exception is thrown during the web application startup. ---------------------------------------------------------- Key: LBCORE-167 URL: http://jira.qos.ch/browse/LBCORE-167 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.24 Environment: Ubuntu 9.04 Reporter: Pavel Mikhalchuk Assignee: Logback dev list Appender is configurated the next way: <appender name="appender class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>some_host</SMTPHost> <BufferSize>10</BufferSize> <To>some(a)email.address</To> <From>som(a)email.address2</From> <Subject>Some subject</Subject> <layout class="ch.qos.logback.classic.html.HTMLLayout"/> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>Some Marker</marker> </evaluator> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="MARKER"> <expression>marker != null && event.getLevel().toInt() >= WARN</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> And when the web application is starting the following stacktrace can be observed: 21:02:57,596 |-ERROR in ch.qos.logback.classic.boolex.JaninoEventEvaluator@1bde392 - Could not start evaluator with expression [marker != null && event.getLevel().toInt() >= WARN.toInt()] org.codehaus.janino.CompileException: Line 2, Column 57: A method named "toInt" is not declared in any enclosing class nor any supertype, nor through a static import at org.codehaus.janino.CompileException: Line 2, Column 57: A method named "toInt" is not declared in any enclosing class nor any supertype, nor through a static import at at org.codehaus.janino.UnitCompiler.compileError(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.findIMethod(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGet2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$51(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$9.visitMethodInvocation(UnitCompiler.java) at at org.codehaus.janino.Java$MethodInvocation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileGet(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGetValue(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileBoolean2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$31(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$7.visitBinaryOperation(UnitCompiler.java) at at org.codehaus.janino.Java$BinaryOperation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileBoolean(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileBoolean2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$31(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$7.visitBinaryOperation(UnitCompiler.java) at at org.codehaus.janino.Java$BinaryOperation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileBoolean(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGet2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGet2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$44(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$9.visitBinaryOperation(UnitCompiler.java) at at org.codehaus.janino.Java$BinaryOperation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileGet(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGetValue(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$17(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$4.visitReturnStatement(UnitCompiler.java) at at org.codehaus.janino.Java$ReturnStatement.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$7(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$4.visitBlock(UnitCompiler.java) at at org.codehaus.janino.Java$Block.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$3.visitPackageMemberClassDeclaration(UnitCompiler.java) at at org.codehaus.janino.Java$PackageMemberClassDeclaration.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileUnit(UnitCompiler.java) at at org.codehaus.janino.SimpleCompiler.compileToClassLoader(SimpleCompiler.java) at at org.codehaus.janino.ClassBodyEvaluator.compileToClass(ClassBodyEvaluator.java) at at org.codehaus.janino.ScriptEvaluator.cook(ScriptEvaluator.java) at at org.codehaus.janino.ScriptEvaluator.cook(ScriptEvaluator.java) at at org.codehaus.janino.Cookable.cook(Cookable.java) at at org.codehaus.janino.Cookable.cook(Cookable.java) at at org.codehaus.janino.Cookable.cook(Cookable.java) at at org.codehaus.janino.ExpressionEvaluator.<init>(ExpressionEvaluator.java) at at ch.qos.logback.core.boolex.JaninoEventEvaluatorBase.start(JaninoEventEvaluatorBase.java:58) at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:168) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at at com.shc.obu.mp.sellpo.batch.ContextListener.<clinit>(ContextListener.java:13) at at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at at java.lang.Class.newInstance0(Class.java:355) at at java.lang.Class.newInstance(Class.java:308) at at org.mortbay.jetty.webapp.WebXmlConfiguration.newListenerInstance(WebXmlConfiguration.java:650) at at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(WebXmlConfiguration.java:631) at at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:368) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.initWebXmlElement(AbstractConfiguration.java:190) at at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.initialize(AbstractConfiguration.java:133) at at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configure(AbstractConfiguration.java:113) at at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configureWebApp(AbstractConfiguration.java:96) at at org.mortbay.jetty.plus.webapp.Configuration.configureWebApp(Configuration.java:149) at at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) at at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at at org.mortbay.jetty.Server.doStart(Server.java:224) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132) at at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:441) at at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:383) at at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210) at at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184) at at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at at java.lang.reflect.Method.invoke(Method.java:597) at at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at at org.codehaus.classworlds.Launcher.main(Launcher.java:375) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at at java.lang.reflect.Method.invoke(Method.java:597) at at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110) The only one right configuration without exceptions is: <appender name="appender class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>some_host</SMTPHost> <BufferSize>10</BufferSize> <To>some(a)email.address</To> <From>som(a)email.address2</From> <Subject>Some subject</Subject> <layout class="ch.qos.logback.classic.html.HTMLLayout"/> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>Some Marker</marker> </evaluator> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="MARKER"> <expression>marker != null && event.getLevel().toInt() >= WARN</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> event.getLevel().toInt() >= WARN (not event.getLevel().toInt() >= WARN.toInt()) But according to http://logback.qos.ch/manual/filters.html#evalutatorFilter we need to use event.getLevel().toInt() >= WARN.toInt(). -- 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 3

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

16 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 74915053db48b5e803816f8d39237cd85293273f (commit) from 9c87bed29ee9f4fe0dd762e897cb0f89b53019de (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=74915053db48b5e803816f8d… http://github.com/ceki/logback/commit/74915053db48b5e803816f8d39237cd852932… commit 74915053db48b5e803816f8d39237cd85293273f Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Sep 16 07:53:41 2010 +0200 In commit 459e776d0ad4954ca36ee26210339ccf61f96f96 dated June 14th 2010 all tests in logback-classic were disabled. Reenabling them. diff --git a/logback-classic/pom.xml b/logback-classic/pom.xml index bd33903..61cd5e2 100644 --- a/logback-classic/pom.xml +++ b/logback-classic/pom.xml @@ -304,7 +304,6 @@ <reportFormat>plain</reportFormat> <trimStackTrace>false</trimStackTrace> <excludes> - <exclude>**/*.java</exclude> <exclude>**/AllClassicTest.java</exclude> <exclude>**/PackageTest.java</exclude> <exclude>**/TestConstants.java</exclude> ----------------------------------------------------------------------- Summary of changes: logback-classic/pom.xml | 1 - 1 files changed, 0 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-17-g9c87bed
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 9c87bed29ee9f4fe0dd762e897cb0f89b53019de (commit) from 462e502759c4e1b794d76a5808b378a05db7c86a (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=9c87bed29ee9f4fe0dd762e8… http://github.com/ceki/logback/commit/9c87bed29ee9f4fe0dd762e897cb0f89b5301… commit 9c87bed29ee9f4fe0dd762e897cb0f89b53019de Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Sep 15 23:22:33 2010 +0200 have all tests pass diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/boolex/JaninoEventEvaluatorTest.java b/logback-classic/src/test/java/ch/qos/logback/classic/boolex/JaninoEventEvaluatorTest.java index 8c18e06..7430f46 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/boolex/JaninoEventEvaluatorTest.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/boolex/JaninoEventEvaluatorTest.java @@ -263,6 +263,7 @@ public class JaninoEventEvaluatorTest { @Test public void nullMDC() throws EvaluationException { + MDC.clear(); jee.setExpression("mdc == null"); jee.start(); ----------------------------------------------------------------------- Summary of changes: .../classic/boolex/JaninoEventEvaluatorTest.java | 1 + 1 files changed, 1 insertions(+), 0 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-16-g462e502
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 462e502759c4e1b794d76a5808b378a05db7c86a (commit) from f6a15779f1a3ad1402460772c30c02d409a6e0fa (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=462e502759c4e1b794d76a58… http://github.com/ceki/logback/commit/462e502759c4e1b794d76a5808b378a05db7c… commit 462e502759c4e1b794d76a5808b378a05db7c86a Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Sep 15 23:17:19 2010 +0200 over 40 months 0.41 day skew per month ads up to 16 days, which causes the tests to fail during the second of september of each year. Oh, yah! diff --git a/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java b/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java index f32b13f..02bc719 100644 --- a/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java +++ b/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java @@ -53,7 +53,7 @@ public class TimeBasedRollingWithArchiveRemovalTest { static final long MILLIS_IN_MINUTE = 60 * 1000; static final long MILLIS_IN_HOUR = 60 * MILLIS_IN_MINUTE; static final long MILLIS_IN_DAY = 24 * MILLIS_IN_HOUR; - static final long MILLIS_IN_MONTH = 30 * MILLIS_IN_DAY; + static final long MILLIS_IN_MONTH = (long) ((365.0/12) * MILLIS_IN_DAY); int diff = RandomUtil.getPositiveInt(); protected String randomOutputDir = CoreTestConstants.OUTPUT_DIR_PREFIX + diff ----------------------------------------------------------------------- Summary of changes: .../TimeBasedRollingWithArchiveRemovalTest.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. v_0.9.24-15-gf6a1577
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 f6a15779f1a3ad1402460772c30c02d409a6e0fa (commit) from 487c8871c3c728dbe7be248a0c81c99d3e4e8fad (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=f6a15779f1a3ad1402460772… http://github.com/ceki/logback/commit/f6a15779f1a3ad1402460772c30c02d409a6e… commit f6a15779f1a3ad1402460772c30c02d409a6e0fa Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Sep 15 22:50:05 2010 +0200 typo fixes diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 8b07ce9..6196232 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -340,7 +340,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl Example: ConsoleAppender configuration (logback-examples/src/main/java/chapters/appenders/conf/logback-Console.xml) - View as .grovvy + View as .groovy <pre id="logback_Console" class="prettyprint source"><configuration> @@ -480,7 +480,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl Example: FileAppender configuration (logback-examples/src/main/java/chapters/appenders/conf/logback-fileAppender.xml) - View as .grovvy + View as .groovy <pre id="logback-fileAppender" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> @@ -523,7 +523,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl configuration by timestamp (logback-examples/src/main/java/chapters/appenders/conf/logback-timestamp.xml) - View as .grovvy + View as .groovy <pre id="logback-timestamp" class="prettyprint source"><configuration>  @@ -1254,7 +1254,7 @@ public interface RollingPolicy extends LifeCycle { <code>SizeAndTimeBasedFNATP</code> (logback-examples/src/main/java/chapters/appenders/conf/logback-sizeAndTime.xml) - View as .grovvy + View as .groovy <pre id="logback-sizeAndTime" class="prettyprint source"><configuration> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>mylog.txt</file> @@ -1363,7 +1363,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { <code>SizeBasedTriggeringPolicy</code> (logback-examples/src/main/java/chapters/appenders/conf/logback-RollingSizeBased.xml) - View as .grovvy + View as .groovy <pre id="logback-RollingSizeBased" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>test.log</file> @@ -1583,7 +1583,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { Example: SocketAppender configuration (logback-examples/src/main/java/chapters/appenders/socket/client1.xml) - View as .grovvy + View as .groovy <pre id="client1" class="prettyprint source"><configuration> <appender name="SOCKET" class="ch.qos.logback.classic.net.SocketAppender"> @@ -2045,7 +2045,7 @@ Context ctx = new InitialContext(env);</pre> Example: JMSTopicAppender configuration (logback-examples/src/main/java/chapters/appenders/conf/logback-JMSTopic.xml) - View as .grovvy + View as .groovy <pre id="logback-JMSTopic" class="prettyprint source"><configuration> <appender name="Topic" @@ -2117,7 +2117,7 @@ Context ctx = new InitialContext(env);</pre> Example: JMSQueueAppender configuration (logback-examples/src/main/java/chapters/appenders/conf/logback-JMSQueue.xml) - View as .grovvy + View as .groovy <pre id="logback-JMSQueue" class="prettyprint source"><configuration> <appender name="Queue" @@ -2341,7 +2341,7 @@ Context ctx = new InitialContext(env);</pre> Example: A sample <code>SMTPAppender</code> configuration (logback-examples/src/main/java/chapters/appenders/mail/mail1.xml) - View as .grovvy + View as .groovy <pre id="mail1" class="prettyprint source"><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>ADDRESS-OF-YOUR-SMTP-HOST</SMTPHost> @@ -2510,7 +2510,7 @@ public class CounterBasedEvaluator extends ContextAwareBase implements EventEval Example: <code>SMTPAppender</code> with custom <code>Evaluator</code> and buffer size (logback-examples/src/main/java/chapters/appenders/mail/mail3.xml) - View as .grovvy + View as .groovy <pre id="mail3" class="prettyprint source"><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <Evaluator class="chapters.appenders.mail.CounterBasedEvaluator" /> @@ -2559,7 +2559,7 @@ logger.error(notifyAdminMarker, Example: <code>SMTPAppender</code> with <code>OnMarkerEvaluator</code> (logback-examples/src/main/java/chapters/appenders/mail/mailWithMarker.xml) - View as .grovvy + View as .groovy <pre id="mailWithMarker" class="prettyprint source"><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> @@ -2608,7 +2608,7 @@ logger.error(notifyAdminMarker, using SSL (logback-examples/src/main/java/chapters/appenders/mail/gmailSSL.xml) - View as .grovvy + View as .groovy <pre id="gmailSSL" class="prettyprint source"><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>smtp.gmail.com</SMTPHost> @@ -2640,7 +2640,7 @@ logger.error(notifyAdminMarker, Example: <code>SMTPAppender</code> to GMAIL using STARTTLS (logback-examples/src/main/java/chapters/appenders/mail/gmailSTARTTLS.xml) - View as .grovvy + View as .groovy <pre id="gmailSTARTTLS" class="prettyprint source"><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>smtp.gmail.com</SMTPHost> @@ -2687,7 +2687,7 @@ logger.error(notifyAdminMarker, MDCBasedDsicriminator (logback-examples/src/main/java/chapters/appenders/mail/mailWithMDCBasedDiscriminator.xml) - View as .grovvy + View as .groovy <pre id="mailWithMDCBasedDiscriminator" class="prettyprint source"><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>ADDRESS-OF-YOUR-SMTP-HOST</SMTPHost> @@ -3013,7 +3013,7 @@ logger.error(notifyAdminMarker, Example: <code>DBAppender</code> configuration (logback-examples/src/main/java/chapters/appenders/db/append-toMySQL-with-driverManager.xml) - View as .grovvy + View as .groovy <pre id="append-toMySQL-with-driverManager" class="prettyprint source"><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -3094,7 +3094,7 @@ logger.error(notifyAdminMarker, Example: <code>DBAppender</code> configuration (logback-examples/src/main/java/chapters/appenders/db/append-with-datasource.xml) - View as .grovvy + View as .groovy <pre id="append-with-datasource" class="prettyprint source"><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -3211,7 +3211,7 @@ logger.error(notifyAdminMarker, without pooling (logback-examples/src/main/java/chapters/appenders/db/append-toMySQL-with-datasource.xml) - View as .grovvy + View as .groovy <pre id="append-toMySQL-with-datasource" class="prettyprint source"><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -3247,7 +3247,7 @@ logger.error(notifyAdminMarker, Example: <code>DBAppender</code> configuration with pooling (logback-examples/src/main/java/chapters/appenders/db/append-toMySQL-with-datasource-and-pooling.xml) - View as .grovvy + View as .groovy <pre id="append-toMySQL-with-datasource-and-pooling" class="prettyprint source"><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -3383,7 +3383,7 @@ logger.error(notifyAdminMarker, Example: <code>SyslogAppender</code> configuration (logback-examples/src/main/java/chapters/appenders/conf/logback-syslog.xml) - View as .grovvy + View as .groovy <pre id="logback-syslog" class="prettyprint source"><configuration> <appender name="SYSLOG" @@ -3443,7 +3443,7 @@ logger.debug("Alice says hello"); configuration (logback-examples/src/main/java/chapters/appenders/sift/byUserid.xml) - View as .grovvy + View as .groovy <pre id="byUserid" class="prettyprint source"><configuration> diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 15bfd2c..769d170 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -622,7 +622,7 @@ public class MyApp3 { Example: Registering a status listener (logback-examples/src/main/java/chapters/configuration/onConsoleStatusListener.xml) - View as .grovvy + View as .groovy <pre id="onConsoleStatusListener" class="prettyprint source"><configuration> <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> @@ -780,7 +780,7 @@ public class MyApp3 { Example: Setting the level of a logger (logback-examples/src/main/java/chapters/configuration/sample2.xml) - View as .grovvy + View as .groovy <pre id="sample2" class="prettyprint source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -821,7 +821,7 @@ public class MyApp3 { Example: Setting the level of multiple loggers (logback-examples/src/main/java/chapters/configuration/sample3.xml) - View as .grovvy + View as .groovy <pre id="sample3" class="source prettyprint"><configuration> <appender name="STDOUT" @@ -894,7 +894,7 @@ public class MyApp3 { href="architecture.html#basic_selection">basic-selection rule</a> depends on the effective level of the logger being invoked, not the level of the logger where appenders are attached. Loback will first - determine wheteher a logging statement is enabled or not, and if + determine whether a logging statement is enabled or not, and if enabled, it will invoke the appenders found in the logger hierarchy, regardless of their level. The configuration file sample4.xml is a case in point: @@ -902,7 +902,7 @@ public class MyApp3 { Example: Logger level sample (logback-examples/src/main/java/chapters/configuration/sample4.xml) - View as .grovvy + View as .groovy <pre id="sample4" class="prettyprint source"><configuration> <appender name="STDOUT" @@ -977,7 +977,7 @@ public class MyApp3 { href="#configuringAppenders">Configuring Appenders</a></h4> An appenders is configured with the <code><appender></code> - element, which takes two mandatroy attributes name and class. The name attribute specifies the name of the appender whereas the class attribute @@ -1028,7 +1028,7 @@ public class MyApp3 { Example: Multiple loggers (logback-examples/src/main/java/chapters/configuration/multiple.xml) - View as .grovvy + View as .groovy <pre id="multiple" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> @@ -1083,7 +1083,7 @@ public class MyApp3 { Example: Duplicate appender (logback-examples/src/main/java/chapters/configuration/duplicate.xml) - View as .grovvy + View as .groovy <pre id="duplicate" class="prettyprint source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -1130,7 +1130,7 @@ public class MyApp3 { Example: Multiple appender (logback-examples/src/main/java/chapters/configuration/restricted.xml) - View as .grovvy + View as .groovy <pre id="restricted" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> @@ -1177,7 +1177,7 @@ public class MyApp3 { Example: Additivity flag (logback-examples/src/main/java/chapters/configuration/additivityFlag.xml) - View as .grovvy + View as .groovy <pre id="additivityFlag" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> @@ -1233,7 +1233,7 @@ public class MyApp3 { Example: Set the context name and display it (logback-examples/src/main/java/chapters/configuration/contextName.xml) - View as .grovvy + View as .groovy <pre id="contextName" class="prettyprint source"><configuration> <contextName>myAppName</contextName> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -1290,7 +1290,7 @@ public class MyApp3 { View as .grovvy + asGroovy('variableSubstitution1');">View as .groovy <pre id="variableSubstitution1" class="prettyprint source"><configuration> <property name="USER_HOME" value="/home/sebastien" /> @@ -1319,7 +1319,7 @@ public class MyApp3 { Example: System Variable substitution (logback-examples/src/main/java/chapters/configuration/variableSubstitution2.xml) - View as .grovvy + View as .groovy <pre id="variableSubstitution2" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> diff --git a/logback-site/src/site/pages/manual/filters.html b/logback-site/src/site/pages/manual/filters.html index c3c59aa..6a7ef15 100644 --- a/logback-site/src/site/pages/manual/filters.html +++ b/logback-site/src/site/pages/manual/filters.html @@ -132,7 +132,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { Example: SampleFilter configuration (logback-examples/src/main/java/chapters/filters/SampleFilterConfig.xml) - View as .grovvy + View as .groovy <pre id="SampleFilterConfig" class="prettyprint source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -189,7 +189,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { Example: Sample LevelFilter configuration (logback-examples/src/main/java/chapters/filters/levelFilterConfig.xml) - View as .grovvy + View as .groovy <pre id="levelFilterConfig" class="prettyprint source"><configuration> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <filter class="ch.qos.logback.classic.filter.LevelFilter"> @@ -222,7 +222,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { Example: Sample ThresholdFilter configuration (logback-examples/src/main/java/chapters/filters/thresholdFilterConfig.xml) - View as .grovvy + View as .groovy <pre id="thresholdFilterConfig" class="prettyprint source"><configuration> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> @@ -304,7 +304,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { Here is a more complete example. - View as .grovvy + View as .groovy <pre id="GEventEvaluator" class="prettyprint source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -522,7 +522,7 @@ public class SampleFilter extends Filter>ILoggingEvent> { Example: Basic event evaluator usage (logback-examples/src/main/java/chapters/filters/basicEventEvaluator.xml) - View as .grovvy + View as .groovy <pre id="basicEventEvaluator" class="prettyprint source longline"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -630,7 +630,7 @@ java chapters.filters.FilterEvents src/main/java/chapters/filters/basicConfigura An example should clarify the point: Example: Defining matchers in an event evaluator (logback-examples/src/main/java/chapters/filters/evaluatorWithMatcher.xml) - View as .grovvy + View as .groovy <pre id="evaluatorWithMatcher" class="prettyprint source"><configuration debug="true"> @@ -787,7 +787,7 @@ public class SampleTurboFilter extends TurboFilter { Example: Basic custom <code>TurboFilter</code> configuration (logback-examples/src/main/java/chapters/filters/sampleTurboFilterConfig.xml) - View as .grovvy + View as .groovy <pre id="sampleTurboFilterConfig" class="prettyprint source"><configuration> <turboFilter class="chapters.filters.SampleTurboFilter"> @@ -827,7 +827,7 @@ public class SampleTurboFilter extends TurboFilter { configuration (logback-examples/src/main/java/chapters/filters/turboFilters.xml) - View as .grovvy + View as .groovy <pre id="turboFilters" class="prettyprint source"><configuration> <turboFilter class="ch.qos.logback.classic.turbo.MDCFilter"> @@ -956,7 +956,7 @@ logger.debug("Hello {}.", name1);</pre> Example: <code>DuplicateMessageFilter</code> configuration (logback-examples/src/main/java/chapters/filters/duplicateMessage.xml) - View as .grovvy + View as .groovy <pre id="duplicateMessage" class="prettyprint source"><configuration> <turboFilter class="ch.qos.logback.classic.turbo.DuplicateMessageFilter"/> diff --git a/logback-site/src/site/pages/manual/layouts.html b/logback-site/src/site/pages/manual/layouts.html index ee5c81b..37e6933 100644 --- a/logback-site/src/site/pages/manual/layouts.html +++ b/logback-site/src/site/pages/manual/layouts.html @@ -160,7 +160,7 @@ public class MySampleLayout extends LayoutBase<ILoggingEvent> { Example: Configuration of MySampleLayout (logback-examples/src/main/java/chapters/layouts/sampleLayoutConfig.xml) - View as .grovvy + View as .groovy <pre id="sampleLayoutConfig" class="prettyprint source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -268,7 +268,7 @@ public class MySampleLayout2 extends LayoutBase<ILoggingEvent> { - View as .grovvy + View as .groovy <pre id="MySampleLayout2" class="prettyprint source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> @@ -1295,7 +1295,7 @@ Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre> (logback-examples/src/main/java/chapters/layouts/callerEvaluatorConfig.xml) - View as .grovvy + View as .groovy <pre id="callerEvaluatorConfig" class="prettyprint source"><configuration> @@ -1605,7 +1605,7 @@ public class MySampleConverter extends ClassicConverter { new conversion word in the configuration file, as shown below: Example: Sample Converter Example (src/main/java/chapters/layouts/mySampleConverterConfig.xml) - View as .grovvy + View as .groovy <pre id="mySampleConverterConfig" class="prettyprint source"><configuration> <conversionRule conversionWord="sample" @@ -1689,7 +1689,7 @@ public class MySampleConverter extends ClassicConverter { Example: HTMLLayout Example (src/main/java/chapters/layouts/htmlLayoutConfig1.xml) -View as .grovvy +View as .groovy <pre id="htmlLayoutConfig1" class="prettyprint source"><configuration debug="true"> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> @@ -1802,7 +1802,7 @@ public class MySampleConverter extends ClassicConverter { Here is a sample configuration Example: Log4jXMLLayout Example (src/main/java/chapters/layouts/log4jXMLLayout.xml) -View as .grovvy +View as .groovy <pre id="log4jXMLLayout" class="prettyprint source"><configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>test.xml</file> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 46 ++++++++++---------- .../src/site/pages/manual/configuration.html | 26 ++++++------ logback-site/src/site/pages/manual/filters.html | 18 ++++---- logback-site/src/site/pages/manual/layouts.html | 12 +++--- 4 files changed, 51 insertions(+), 51 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0