October 2009 - logback-dev - mailman3.qos.ch

branch, master, updated. 7746ef887110ae043226be2b6cc78c7c28b66df8
by git-noreply＠pixie.qos.ch 16 Oct '09

16 Oct '09

The branch, master has been updated via 7746ef887110ae043226be2b6cc78c7c28b66df8 (commit) via 23abd09c563b9f6c84716d5c17005db9f5f3ebc4 (commit) from d3e8a64dce1edb3c769101d874cae1f090f3021b (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=7746ef887110ae043226be2b… http://github.com/ceki/logback/commit/7746ef887110ae043226be2b6cc78c7c28b66… commit 7746ef887110ae043226be2b6cc78c7c28b66df8 Merge: 23abd09 d3e8a64 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Oct 16 18:50:27 2009 +0200 Merge branch 'master' of git.qos.ch:logback http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=23abd09c563b9f6c84716d5c… http://github.com/ceki/logback/commit/23abd09c563b9f6c84716d5c17005db9f5f3e… commit 23abd09c563b9f6c84716d5c17005db9f5f3ebc4 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Oct 16 18:50:15 2009 +0200 merged logback-announce into announce(a)qos.ch diff --git a/logback-site/src/site/pages/mailinglist.html b/logback-site/src/site/pages/mailinglist.html index 7a7268b..c03f6fe 100644 --- a/logback-site/src/site/pages/mailinglist.html +++ b/logback-site/src/site/pages/mailinglist.html @@ -62,33 +62,25 @@ <th>Archives</th> </tr> <tr class="b"> - <td>Logback Announce List</td> + <td>QOS.ch announce List</td> <td>Low</td> <td> <a - href="http://qos.ch/mailman/listinfo/logback-announce"> + href="http://qos.ch/mailman/listinfo/announce"> Subscribe </a> </td> <td> <a - href="http://qos.ch/mailman/options/logback-announce"> + href="http://qos.ch/mailman/options/announce"> Unsubscribe </a> </td> <td> <a - href="http://www.qos.ch/pipermail/logback-announce/"> + href="http://www.qos.ch/pipermail/announce/"> qos.ch - </a> | - <a - href="http://marc.theaimsgroup.com/?l=logback-announce"> - MARC - </a> | - <a - href="http://www.nabble.com/Logback-Announce-f16251.html"> - Nabble - </a> + </a> </td> </tr> <tr class="a"> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/mailinglist.html | 18 +++++------------- 1 files changed, 5 insertions(+), 13 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-162) Typo in ClassicConstants
by Joern Huxhorn (JIRA) 15 Oct '09

15 Oct '09

Typo in ClassicConstants ------------------------ Key: LBCLASSIC-162 URL: http://jira.qos.ch/browse/LBCLASSIC-162 Project: logback-classic Issue Type: Improvement Components: Other Affects Versions: 0.917 Reporter: Joern Huxhorn Assignee: Logback dev list Priority: Minor ch.qos.logback.classic.ClassicConstants.DEFAULT_MAX_CALLEDER_DATA_DEPTH should be DEFAULT_MAX_CALLER_DATA_DEPTH. -- 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

Some documentation shortcomings and a typo...
by Joern Huxhorn 15 Oct '09

15 Oct '09

Hi Ceki, I just realized that the documentation is missing info about how to disable packaging data and how to set maxCallerDataDepth. I wasn't able to find it, at least. On a side note, I also saw that there's a typo in ClassicConstants.DEFAULT_MAX_CALLEDER_DATA_DEPTH ;) Regards, Joern.

2 2

[JIRA] Created: (LBCLASSIC-161) Documentation is missing information how to set maxCallerDataDepth
by Joern Huxhorn (JIRA) 15 Oct '09

15 Oct '09

Documentation is missing information how to set maxCallerDataDepth ------------------------------------------------------------------ Key: LBCLASSIC-161 URL: http://jira.qos.ch/browse/LBCLASSIC-161 Project: logback-classic Issue Type: Improvement Components: Other Affects Versions: 0.917 Reporter: Joern Huxhorn Assignee: Logback dev list -- 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

[JIRA] Created: (LBCLASSIC-160) Documentation is missing information how to disable classPackagingData in Throwable StackTraceElements
by Joern Huxhorn (JIRA) 15 Oct '09

15 Oct '09

Documentation is missing information how to disable classPackagingData in Throwable StackTraceElements ------------------------------------------------------------------------------------------------------ Key: LBCLASSIC-160 URL: http://jira.qos.ch/browse/LBCLASSIC-160 Project: logback-classic Issue Type: Improvement Components: Other Affects Versions: 0.917 Reporter: Joern Huxhorn Assignee: Logback dev list -- 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

branch, master, updated. d3e8a64dce1edb3c769101d874cae1f090f3021b
by git-noreply＠pixie.qos.ch 14 Oct '09

14 Oct '09

The branch, master has been updated via d3e8a64dce1edb3c769101d874cae1f090f3021b (commit) via 79cf4f778bceef507f145ea4b66f07a9ee4600da (commit) from 3ad0c4474488b4c967e504acb7b9598200a5a048 (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=d3e8a64dce1edb3c769101d8… http://github.com/ceki/logback/commit/d3e8a64dce1edb3c769101d874cae1f090f30… commit d3e8a64dce1edb3c769101d874cae1f090f3021b Merge: 79cf4f7 3ad0c44 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Oct 14 23:11:49 2009 +0200 Merge branch 'master' of git.qos.ch:logback http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=79cf4f778bceef507f145ea4… http://github.com/ceki/logback/commit/79cf4f778bceef507f145ea4b66f07a9ee460… commit 79cf4f778bceef507f145ea4b66f07a9ee4600da Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Oct 14 23:10:48 2009 +0200 - pom packaging is more appropriate for the logback-sire module - editing bugreport.html and license.html diff --git a/logback-site/pom.xml b/logback-site/pom.xml index 7f118ae..3da1644 100644 --- a/logback-site/pom.xml +++ b/logback-site/pom.xml @@ -10,7 +10,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-site</artifactId> - <packaging>jar</packaging> + <packaging>pom</packaging> <version>${parent.version}</version> <name>Logback Site</name> diff --git a/logback-site/src/site/pages/bugreport.html b/logback-site/src/site/pages/bugreport.html index dbc779f..cea7681 100644 --- a/logback-site/src/site/pages/bugreport.html +++ b/logback-site/src/site/pages/bugreport.html @@ -68,15 +68,15 @@ for logback bugs</a></li> </ul> - <h2>Reporting with bugs</h2> + <h3>Reporting a bug</h3> <p>Only after you have exhausted the aforementioned steps, should you file a formal report in JIRA, our bug tracking system. </p> <p>Please make sure you provide as much information as possible. - Its very hard to fix a bug if the person looking into the problem - can't reproduce it. + It is hard to fix a bug if the person looking into the problem + cannot reproduce it. </p> <ul> diff --git a/logback-site/src/site/pages/license.html b/logback-site/src/site/pages/license.html index 0bc88a2..af320a8 100644 --- a/logback-site/src/site/pages/license.html +++ b/logback-site/src/site/pages/license.html @@ -48,14 +48,15 @@ as published by the Free Software Foundation.</p> </p> <p>The EPL/LGPL dual-license serves several purposes. The LGPL - license ensures <em>continuity</em> in tems of licensing of the + license ensures <em>continuity</em> in terms of licensing of the logback project. Prior to version 0.9.18, logback was licensed (exlusively) under the LGPL v2.1. Moreover, since the EPL is deemed <a href="http://www.fsf.org/licensing/licenses/index_htm">incompatible</a> by the Free Software Foundation, the LGPL will allow various - licensees, in particular software distributors, who may be already - bound by the terms of the GPL or the LGPL. + licensees, in particular software distributors who may be already + bound by the terms of the GPL or the LGPL, to distribute our + software. </p> <p>On the other hand, the EPL license will placate organizations ----------------------------------------------------------------------- Summary of changes: logback-site/pom.xml | 2 +- logback-site/src/site/pages/bugreport.html | 6 +++--- logback-site/src/site/pages/license.html | 7 ++++--- 3 files changed, 8 insertions(+), 7 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBGENERAL-34) LoggingEventSerializationPerfTest failed.
by Ralph Goers (JIRA) 14 Oct '09

14 Oct '09

LoggingEventSerializationPerfTest failed. ----------------------------------------- Key: LBGENERAL-34 URL: http://jira.qos.ch/browse/LBGENERAL-34 Project: logback-general Issue Type: Sub-task Affects Versions: 0.9.17 Environment: Mac OSX Reporter: Ralph Goers Assignee: Logback dev list ------------------------------------------------------------------------------- Test set: ch.qos.logback.classic.spi.LoggingEventSerializationPerfTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.894 sec <<< FAILURE! testPerformance(ch.qos.logback.classic.spi.LoggingEventSerializationPerfTest) Time elapsed: 0.363 sec testPerformanceWithParameters(ch.qos.logback.classic.spi.LoggingEventSerializationPerfTest) Time elapsed: 0.514 sec <<< FAILURE! junit.framework.AssertionFailedError: current duration 7681.4 exceeded expected 2332.89 (adjusted reference), 7000 (raw reference) at org.slf4j.helpers.BogoPerf.assertDuration(BogoPerf.java:121) at ch.qos.logback.classic.spi.LoggingEventSerializationPerfTest.testPerformanceWithParameters(LoggingEventSerializationPerfTest.java:135) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) -- 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

[JIRA] Created: (LBGENERAL-32) TimeBasedRollingWithConfigFileTest failure
by Ralph Goers (JIRA) 14 Oct '09

14 Oct '09

TimeBasedRollingWithConfigFileTest failure ------------------------------------------ Key: LBGENERAL-32 URL: http://jira.qos.ch/browse/LBGENERAL-32 Project: logback-general Issue Type: Sub-task Affects Versions: 0.9.17 Environment: Mac OSX Reporter: Ralph Goers Assignee: Logback dev list ------------------------------------------------------------------------------- Test set: ch.qos.logback.classic.rolling.TimeBasedRollingWithConfigFileTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec <<< FAILURE! basic(ch.qos.logback.classic.rolling.TimeBasedRollingWithConfigFileTest) Time elapsed: 0.048 sec timeAndSize(ch.qos.logback.classic.rolling.TimeBasedRollingWithConfigFileTest) Time elapsed: 0.04 sec <<< FAILURE! java.lang.AssertionError: eCount=4expectedFilenameList.size=6 at org.junit.Assert.fail(Assert.java:74) at org.junit.Assert.assertTrue(Assert.java:37) at ch.qos.logback.classic.rolling.TimeBasedRollingWithConfigFileTest.timeAndSize(TimeBasedRollingWithConfigFileTest.java:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) -- 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

Another unit test failure - TimeBasedRollingWithArchiveRemovalTe
by Ralph Goers 14 Oct '09

14 Oct '09

I have no idea what is going on here. I know my machine is a lot faster than yours but having these unit tests randomly fail is very annoying. ------------------------------------------------------------------------------- Test set: ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest ------------------------------------------------------------------------------- Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.411 sec <<< FAILURE! montlyRollover (ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.114 sec montlyRolloverOverManyPeriods (ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.253 sec dailyRollover (ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.058 sec dailyCronologRollover (ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.108 sec dailySizeBasedRollover (ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.454 sec dailyChronologSizeBasedRollover (ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Time elapsed: 0.417 sec <<< ERROR! java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask$Sync.innerGet (FutureTask.java:228) at java.util.concurrent.FutureTask.get(FutureTask.java:91) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.doRollover (TimeBasedRollingWithArchiveRemovalTest.java:194) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.dailyChronologSizeBasedRollover (TimeBasedRollingWithArchiveRemovalTest.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke (TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod (MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run (MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters (MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest (MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run (MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod (JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods (JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run (JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected (ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected (ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run (JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute (JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet (AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute (AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess (SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main (SurefireBooter.java:997)

3 3

[JIRA] Created: (LBGENERAL-31) Unit tests fail depending on the host
by Ceki Gulcu (JIRA) 14 Oct '09

14 Oct '09

Unit tests fail depending on the host ------------------------------------- Key: LBGENERAL-31 URL: http://jira.qos.ch/browse/LBGENERAL-31 Project: logback-general Issue Type: Bug Affects Versions: 0.9.17 Reporter: Ceki Gulcu Assignee: Logback dev list Unit tests fail from time to time depending on the host machine and other external factors. -- 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