- logback-dev - mailman3.qos.ch

[qos-ch/logback] 91ffa4: minor optimization
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 91ffa4f9f9a2399343554a1b6791baa601f70706 https://github.com/qos-ch/logback/commit/91ffa4f9f9a2399343554a1b6791baa601… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java Log Message: ----------- minor optimization

1 0

[JIRA] (LBCLASSIC-333) add stacktraceSuffixPattern
by Ingebrigt Berg (JIRA) 31 May '12

31 May '12

2 3

[qos-ch/logback] 246567: start working on 1.0.5-SNAPSHOT
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 2465675e48b70f07c268ede3158cca7b1d8ce2d8 https://github.com/qos-ch/logback/commit/2465675e48b70f07c268ede3158cca7b1d… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 2012) Changed paths: M logback-access/pom.xml M logback-classic/pom.xml M logback-core/pom.xml M logback-examples/pom.xml M logback-site/pom.xml M pom.xml Log Message: ----------- start working on 1.0.5-SNAPSHOT

1 0

[qos-ch/logback]
by ceki 31 May '12

31 May '12

Branch: refs/tags/v_1.0.4 Home: https://github.com/qos-ch/logback

1 0

[qos-ch/logback] a773d9: minor correction
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: a773d9620f052a024285589c93cec345cddaab6b https://github.com/qos-ch/logback/commit/a773d9620f052a024285589c93cec345cd… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 2012) Changed paths: M logback-access/pom.xml M logback-classic/pom.xml M logback-core/pom.xml M logback-examples/pom.xml M logback-site/pom.xml M logback-site/src/site/pages/news.html M pom.xml Log Message: ----------- minor correction

1 0

Release of logback version 1.0.4
by ceki 31 May '12

31 May '12

Hello all, I am thrilled to announce the release of logback version 1.0.4. It should hit the Maven central repository within the next 24 hours. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki http://twitter.com/#!/ceki

1 0

[JIRA] Created: (LBCLASSIC-327) SyslogAppender doesn't respect %nopex, outputs stack trace
by Don Faulkner (JIRA) 31 May '12

31 May '12

SyslogAppender doesn't respect %nopex, outputs stack trace ---------------------------------------------------------- Key: LBCLASSIC-327 URL: http://jira.qos.ch/browse/LBCLASSIC-327 Project: logback-classic Issue Type: Bug Components: appender, layout Affects Versions: 1.0.0 Environment: Ubuntu (11.10) & Red Hat (RHEL 5.8) Linux, Java 1.6, Shibboleth Identity Provider 2.3.6 Reporter: Don Faulkner Assignee: Logback dev list (See http://mailman.qos.ch/pipermail/logback-user/2012-April/003096.html) When using SyslogAppender, stack trace output appears in the output of the Appender, contrary to the configured (or programmed) layout. When my SyslogAppender is used, stack traces appear in my syslog output, even though I don't want them. I've included a "%nopex" at the end of the SuffixPattern value, but this has not stopped the stack traces from appearing. I've tested a matching RollingFileAppender, where "%nopex" has the expected behavior. I'd expect that SyslogAppender would omit stack traces by default, or at least give me a way to omit them. I've looked at the source for SyslogAppender.java, and I see (about line 43) that the prefixPattern already includes "%nopex" so I'm at a loss as to why I'm seeing stack traces to begin with. I've configured a SyslogAppender as follows. The "%nopex" at the end doesn't matter. I can leave it out with identical results. The blank space at the beginning of SuffixPattern doesn't matter either. I can leave it out with identical results. <appender name="IDP_SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> <SyslogHost>localhost</SyslogHost> <Port>514</Port> <Facility>AUTH</Facility> <SuffixPattern> [%logger:%level] %msg %mdc{idpSessionId} from %mdc{clientIP}%nopex</SuffixPattern> </appender> -- 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

5 4

[qos-ch/logback] 911696: fix LBCLASSIC-327 and LBCLASSIC-333
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 91169695a584879efe8f3ba9665580db48f8faa9 https://github.com/qos-ch/logback/commit/91169695a584879efe8f3ba9665580db48… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java M logback-classic/src/test/java/ch/qos/logback/classic/PackageTest.java M logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java M logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java M logback-core/src/test/java/ch/qos/logback/core/PackageTest.java M logback-site/src/site/pages/manual/appenders.html M logback-site/src/site/pages/news.html Log Message: ----------- fix LBCLASSIC-327 and LBCLASSIC-333

1 0

[qos-ch/logback] b1ac43: adding stacktraceSuffixPattern property to SyslogA...
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: b1ac439e2259a83840ee4c42972993d263620047 https://github.com/qos-ch/logback/commit/b1ac439e2259a83840ee4c42972993d263… Author: ingebrigt <ingebrigt(a)jpro.no> Date: 2012-04-12 (Thu, 12 Apr 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java M logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java M logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java Log Message: ----------- adding stacktraceSuffixPattern property to SyslogAppender Commit: ec00b02d5a936a038f35bda7549ab1d7da156ec7 https://github.com/qos-ch/logback/commit/ec00b02d5a936a038f35bda7549ab1d7da… Author: ingebrigt <ingebrigt(a)jpro.no> Date: 2012-04-13 (Fri, 13 Apr 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java M logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java Log Message: ----------- added a stacktraceLayout and improved testing of stacktrace message lines Commit: e9e064031f187ad6f4adcc0e2a3c5938f432ce30 https://github.com/qos-ch/logback/commit/e9e064031f187ad6f4adcc0e2a3c5938f4… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java M logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java M logback-core/src/main/java/ch/qos/logback/core/net/SyslogAppenderBase.java Log Message: ----------- Merge pull request #46 from ingebrigt/master adding stacktrace suffix to syslogappender Compare: https://github.com/qos-ch/logback/compare/f495e50...e9e0640

1 0

[JIRA] Created: (LBCORE-92) Implement AsyncAppender
by Cheenu (JIRA) 31 May '12

31 May '12

Implement AsyncAppender ----------------------- Key: LBCORE-92 URL: http://jira.qos.ch/browse/LBCORE-92 Project: logback-core Issue Type: Improvement Components: Appender Reporter: Cheenu Assignee: Logback dev list Please implement AsyncAppender as in log4j. http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/AsyncAppender.… Some flaws noted in the log4j appender (I don't agree with silently throwing away log messages being default though) http://glueclue.blogspot.com/2007/01/log4j-asyncappender-is-not-always_31.h… Referenced from #LBCLASSIC-20 Thanks -- 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

5 6