- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1064) wrong log filename
by Daan (JIRA) 16 Apr '15

16 Apr '15

1 0

[JIRA] (LOGBACK-1064) wrong log filename
by Daan (JIRA) 15 Apr '15

15 Apr '15

1 0

[qos-ch/logback] 467ecc: Fixed timing issue in JettyBasicTest
by Tony Trinh 15 Apr '15

15 Apr '15

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 467ecc7212e903608f56f34a69cc821794c9a3cc https://github.com/qos-ch/logback/commit/467ecc7212e903608f56f34a69cc821794… Author: Alex Panchenko <alex.panchenko(a)gmail.com> Date: 2015-04-13 (Mon, 13 Apr 2015) Changed paths: M logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java M logback-access/src/test/java/ch/qos/logback/access/testUtil/NotifyingListAppender.java Log Message: ----------- Fixed timing issue in JettyBasicTest Commit: d46efd0ebd856924a51b9638cc374687c6f438c8 https://github.com/qos-ch/logback/commit/d46efd0ebd856924a51b9638cc374687c6… Author: Tony Trinh <tony19(a)gmail.com> Date: 2015-04-15 (Wed, 15 Apr 2015) Changed paths: M logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java M logback-access/src/test/java/ch/qos/logback/access/testUtil/NotifyingListAppender.java Log Message: ----------- Merge pull request #253 from panchenko/jetty-test-timing Fixed timing issue in JettyBasicTest Compare: https://github.com/qos-ch/logback/compare/42d1b1cfab40...d46efd0ebd85

1 0

[qos-ch/logback] 3d5cf2: Optimization: use Collections.emptyMap() in Loggin...
by Tony Trinh 15 Apr '15

15 Apr '15

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 3d5cf2e0eb4f8d6cdd9ff9b646af5c870c960ba4 https://github.com/qos-ch/logback/commit/3d5cf2e0eb4f8d6cdd9ff9b646af5c870c… Author: Alex Panchenko <alex.panchenko(a)gmail.com> Date: 2015-04-13 (Mon, 13 Apr 2015) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java Log Message: ----------- Optimization: use Collections.emptyMap() in LoggingEvent Commit: 42d1b1cfab40ee1f1303aa34bf0b62b81f49d40c https://github.com/qos-ch/logback/commit/42d1b1cfab40ee1f1303aa34bf0b62b81f… Author: Tony Trinh <tony19(a)gmail.com> Date: 2015-04-15 (Wed, 15 Apr 2015) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java Log Message: ----------- Merge pull request #252 from panchenko/emptyMap Optimization: use Collections.emptyMap() in LoggingEvent Compare: https://github.com/qos-ch/logback/compare/985257ffc78f...42d1b1cfab40

1 0

Setting the logger level through JMX not working (duplicated context)
by Sergio Pintos 14 Apr '15

14 Apr '15

Hi, While setting the logger level through the JConsole (via jmx), the JConsole applies the operation successfully but nothing happens on the actual logger implementation. Apparently, there are two LoggerContext instances on the classloader. I don't know if this is normal or not. I'm debugging logack and I'm seeing that the Logger's object instance the JConsole is using is different than the instance used by my application. I have some screenshots so you can get a better understanding of this: This is while setting the logger lvl through the JConsole: Parent Logger: http://image.gxzone.com/images/2/7/27755de3ab7.png Logger Context: http://image.gxzone.com/images/4/e/4ee00ced572.png Children List: http://image.gxzone.com/images/3/e/3e27e1cc19d.png This is while trying to log from my application: Child Logger: http://image.gxzone.com/images/5/5/55c5e233a0e.png Parent Logger: http://image.gxzone.com/images/3/b/3b6428908e0.png You can also see the logger's context on these images. The id's that eclipse is showing are different on each case, thus we have two object instances of the Logger and Logger Context. I really appreciate if you guys could help me out since I've been working on this several days and I'm stuck. Thanks, Sergio.

1 1

[JIRA] (LOGBACK-1061) jvm process not exiting when using logback 1.0.11+
by Pavel (JIRA) 10 Apr '15

10 Apr '15

1 0

[qos-ch/logback] 667fa0: fixes viewAsGroovy Link for configurations with st...
by Tony Trinh 09 Apr '15

09 Apr '15

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 667fa0160dfae08c4d73601103f1d2c3bac82755 https://github.com/qos-ch/logback/commit/667fa0160dfae08c4d73601103f1d2c3ba… Author: Klaus Bayrhammer <bayrhammer.klaus(a)gmail.com> Date: 2015-04-08 (Wed, 08 Apr 2015) Changed paths: M logback-site/src/site/pages/js/dsl.js Log Message: ----------- fixes viewAsGroovy Link for configurations with styling * modifies ignore-regex in order to ignore <span> tags correctly Commit: 985257ffc78f0c0076792e10f4fcc858c264ef75 https://github.com/qos-ch/logback/commit/985257ffc78f0c0076792e10f4fcc858c2… Author: Tony Trinh <tony19(a)gmail.com> Date: 2015-04-08 (Wed, 08 Apr 2015) Changed paths: M logback-site/src/site/pages/js/dsl.js Log Message: ----------- Merge pull request #251 from klausbayrhammer/fixViewAsGroovyLink fixes viewAsGroovy Link for configurations with styling Compare: https://github.com/qos-ch/logback/compare/efa0cafa97c5...985257ffc78f

1 0

[JIRA] (LOGBACK-880) AccessControlException when logback tries to execute PackagingDataCalculator.populateFrames(..)
by Heiko Kundlacz (JIRA) 08 Apr '15

08 Apr '15

1 0

Fixed: qos-ch/logback#127 (master - efa0caf)
by Travis CI 08 Apr '15

08 Apr '15

Build Update for qos-ch/logback ------------------------------------- Build: #127 Status: Fixed Duration: 1 minute and 48 seconds Commit: efa0caf (master) Author: Tony Trinh Message: Fix unit test errors related to missing packaging data The following unit tests were failing because they were expecting the logger context to have package data enabled by default, but the default had been changed to false in 8141f88edb95567c2b42bbc73aa81e9eeb399169. * ExtendedThrowableProxyConverterTest.integration * RootCauseFirstThrowableProxyConverterTest.integration This patch explicitly enables packaging data for the test's logger context. View the changeset: https://github.com/qos-ch/logback/compare/a7890cfce1bb...efa0cafa97c5 View the full build log and details: https://travis-ci.org/qos-ch/logback/builds/57606755 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications

1 0

[qos-ch/logback] efa0ca: Fix unit test errors related to missing packaging ...
by Tony Trinh 08 Apr '15

08 Apr '15

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: efa0cafa97c5615780d1048f2fcf1f95da01d57a https://github.com/qos-ch/logback/commit/efa0cafa97c5615780d1048f2fcf1f95da… Author: Tony Trinh <tony19(a)gmail.com> Date: 2015-04-08 (Wed, 08 Apr 2015) Changed paths: M logback-classic/src/test/java/ch/qos/logback/classic/pattern/ExtendedThrowableProxyConverterTest.java M logback-classic/src/test/java/ch/qos/logback/classic/pattern/RootCauseFirstThrowableProxyConverterTest.java Log Message: ----------- Fix unit test errors related to missing packaging data The following unit tests were failing because they were expecting the logger context to have package data enabled by default, but the default had been changed to false in 8141f88edb95567c2b42bbc73aa81e9eeb399169. * ExtendedThrowableProxyConverterTest.integration * RootCauseFirstThrowableProxyConverterTest.integration This patch explicitly enables packaging data for the test's logger context.

1 0