- slf4j-dev - mailman3.qos.ch

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-18-gee03248
by git-noreply＠pixie.qos.ch 27 Dec '10

27 Dec '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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via ee03248c91eb6ac053ee68668c80d0a0f7ef29a6 (commit) from be523b4077d0351ee226bc94febed0ea0af64a8c (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=slf4j.git;a=commit;h=ee03248c91eb6ac053ee68668c… http://github.com/ceki/slf4j/commit/ee03248c91eb6ac053ee68668c80d0a0f7ef29a6 commit ee03248c91eb6ac053ee68668c80d0a0f7ef29a6 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Dec 27 16:11:30 2010 +0100 clean up diff --git a/slf4j-site/src/site/pages/docs.html b/slf4j-site/src/site/pages/docs.html index c3ad212..f81bf0d 100644 --- a/slf4j-site/src/site/pages/docs.html +++ b/slf4j-site/src/site/pages/docs.html @@ -63,18 +63,12 @@ Guice</a>, by Michael Glauche </li> <li> - <a href="slf4j-in-10-slides.ppt">JUnit 4 Test Logging Tips using - SLF4J</a>, by Ceki Gülc&uuml + <a href="slf4j-in-10-slides.ppt">SLF4J in 10 slides</a>, by Ceki Gülcü </li> - <li> - <a - href="http://www.devoxx.com:5080/player/main.html#state=state_player&id=357&slide…">SLF4J - and Logback projects</a>, by C. Gülcü and S. Pennec - (Jazoon presentation with audio). If the previous link does not - work, please try the <a - href="http://beta.parleys.com/share/parleysshare2.swf?pageId=357">back - up</a>. + <li><a + href="http://beta.parleys.com/#id=1701&st=5&sl=1"><b>Devoxx-2009 + video presentaion</b></a>, by Ceki Gülcü </li> <li> @@ -110,12 +104,7 @@ <a href="http://baptiste-wicht.developpez.com/tutorials/java/slf4j/">Logging with SLF4J</a> by Baptiste Wicht </li> - - <li> - <a - href="http://sharein.com/shares/111630-a-java-geek-thoughts-on-java-logging-and-s…">Logging: - should I wrap?</a> by Chris Wong - </li> + </ul> <h4>In French</h4> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/docs.html | 21 +++++---------------- 1 files changed, 5 insertions(+), 16 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

Mail System Error - Returned Mail
by Automatic Email Delivery Software 27 Dec '10

27 Dec '10

The message was not delivered due to the following reason: Your message could not be delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 3 days: Host 136.90.201.157 is not responding. The following recipients could not receive this message: <dev(a)slf4j.org> Please reply to postmaster(a)slf4j.org if you feel this message to be in error.

1 0

[Bug 133] Add ability to log at a dynamic level
by bugzilla-daemon＠pixie.qos.ch 24 Dec '10

24 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=133 Gyorgy Orban <gyorgy.orban(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gyorgy.orban(a)gmail.com Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #5 from Gyorgy Orban <gyorgy.orban(a)gmail.com> 2010-12-24 12:40:36 --- Any update on this? Robert and Zoltan gave valid use-cases here for having a log method that takes a level parameter. At the moment SLF4J forces people to come up with hacky solutions to this, which is a design flaw. I just stumbled upon another use-case: if I want an AOP based logging solution where I can parameterize the log levels I need to do the same hack again... -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-17-gbe523b4
by git-noreply＠pixie.qos.ch 22 Dec '10

22 Dec '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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via be523b4077d0351ee226bc94febed0ea0af64a8c (commit) from 9d2796d04333e3790cc6f8d30d0b003a34ff942a (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=slf4j.git;a=commit;h=be523b4077d0351ee226bc94fe… http://github.com/ceki/slf4j/commit/be523b4077d0351ee226bc94febed0ea0af64a8c commit be523b4077d0351ee226bc94febed0ea0af64a8c Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Dec 22 18:10:09 2010 +0100 improved working diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html index bcbd015..777a7ba 100644 --- a/slf4j-site/src/site/pages/codes.html +++ b/slf4j-site/src/site/pages/codes.html @@ -160,6 +160,11 @@ to use the nop (no-operation) binding, then remove <em>slf4j-simple-${version}.jar</em> from the class path.</p> + <p>Note that the warning emitted by SLF4J is just that, a + warning. SLF4J will still bind with the first framework it finds + on the class path. + </p> +  <h3> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/codes.html | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[Bug 31] Varargs for Logger methods
by bugzilla-daemon＠pixie.qos.ch 14 Dec '10

14 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=31 Sean Flanigan <sflaniga(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sflaniga(a)redhat.com -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 210] New: Illegal Access to SINGLETON field
by bugzilla-daemon＠pixie.qos.ch 13 Dec '10

13 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=210 Summary: Illegal Access to SINGLETON field Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: dsills(a)datasourceinc.com While running a JUnit test using SLF4J 1.6.1 under Java 1.4.2, I was unable to proceed because the lines 49-53 of the StaticLoggerBinder in the log4j-over-slf4j JAR file (well, the source for that class) read: /** * The unique instance of this class. * */ private static final StaticLoggerBinder SINGLETON = new StaticLoggerBinder(); The private variable was somehow involved in what the LoggerFactory was doing. Following a suggestion on the web, I replaced this line with: /** * The unique instance of this class. * */ public static final StaticLoggerBinder SINGLETON = new StaticLoggerBinder(); and everything works great. It may be that there's a reason to keep the SINGLETON private, but one cannot use the logger in that case, as the JVM at runtime throws an IllegalAccessException. However, it seems (though I can find no specific reason why this might be the case) that the LoggerFactory must itself be recompiled in conjunction with this change in order to work. It may be that SLF4J 1.6.1 shouldn't run under 1.4.2 (though I see nothing that forbids it), but if it should, this one-line change would make, I would think, a significant difference. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 209] New: Java 5 API used
by bugzilla-daemon＠pixie.qos.ch 13 Dec '10

13 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=209 Summary: Java 5 API used Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: dsills(a)datasourceinc.com I noted when running a JUnit test using SLF4J 1.6.1 under Java 1.4.2 that a Java 5 API method was used, which created a problem but did not prevent logging altogether, simply printed out a stack trace. It should be no great issue to fix, I should think: Unexpected problem occured during version sanity check Reported exception: java.lang.NoSuchMethodError: java.util.Arrays.toString([Ljava/lang/Object;)Ljava/lang/String; at org.slf4j.LoggerFactory.versionSanityCheck(LoggerFactory.java:161) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:106) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:235) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:208) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:221) at com.datasourceinc.alerts.util.AlertsFileParser.<init>(AlertsFileParser.java:15) at com.datasourceinc.alerts.util.FileParsingTest.testParse(FileParsingTest.java:19) 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:324) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) (BTW, I note that Windows 7 is not on your OS list and used Windows XP so as to come as close as I could.) -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-16-g9d2796d
by git-noreply＠pixie.qos.ch 09 Dec '10

09 Dec '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 "SLF4J: Simple Logging Facade for Java". The branch, master has been updated via 9d2796d04333e3790cc6f8d30d0b003a34ff942a (commit) from b6e0c251129fb0eb4da237cbb9a99517599b6f5d (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=slf4j.git;a=commit;h=9d2796d04333e3790cc6f8d30d… http://github.com/ceki/slf4j/commit/9d2796d04333e3790cc6f8d30d0b003a34ff942a commit 9d2796d04333e3790cc6f8d30d0b003a34ff942a Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Dec 9 11:31:24 2010 +0100 added the isInstalled method to SLF4JBridgeHandler diff --git a/jul-to-slf4j/src/main/java/org/slf4j/bridge/SLF4JBridgeHandler.java b/jul-to-slf4j/src/main/java/org/slf4j/bridge/SLF4JBridgeHandler.java index 850b989..73f6373 100644 --- a/jul-to-slf4j/src/main/java/org/slf4j/bridge/SLF4JBridgeHandler.java +++ b/jul-to-slf4j/src/main/java/org/slf4j/bridge/SLF4JBridgeHandler.java @@ -140,6 +140,24 @@ public class SLF4JBridgeHandler extends Handler { } } + /** + * Returns true if SLF4JBridgeHandler has been previously installed, returns false otherwise. + * @return + * @throws SecurityException + */ + public static boolean isInstalled() throws SecurityException { + java.util.logging.Logger rootLogger = LogManager.getLogManager().getLogger( + ""); + Handler[] handlers = rootLogger.getHandlers(); + for (int i = 0; i < handlers.length; i++) { + if (handlers[i] instanceof SLF4JBridgeHandler) { + return true; + } + } + return false; + } + + /** * Initialize this handler. * ----------------------------------------------------------------------- Summary of changes: .../java/org/slf4j/bridge/SLF4JBridgeHandler.java | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+), 0 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

slf4j compatibility reports
by Andrey Ponomarenko 08 Dec '10

08 Dec '10

Hello, I've seen slf4j compatibility reports at [1] computed by the Clirr tool and just want to inform you about our alternative test results at [2]. Our tools are very young and may produce false positives/negatives at the moment, but the slf4j expert is needed to verify it. If you are still interested in backward compatibility then tell me please your feedback/suggestions about our tests. Thanks! [1] http://www.slf4j.org/compatibility.html [2] http://linuxtesting.org/upstream-tracker/java/versions/slf4j.html -- Andrey Ponomarenko Department for Operating Systems at ISPRAS web: http://www.LinuxTesting.org mail: aponomarenko(a)ispras.ru

1 0

Returned mail: see transcript for details
by Mail Administrator 08 Dec '10

08 Dec '10

The original message was received at Wed, 8 Dec 2010 13:56:13 +0800 from 23.98.180.10 ----- The following addresses had permanent fatal errors ----- dev(a)slf4j.org ----- Transcript of session follows ----- ... while talking to slf4j.org.: 554 <dev(a)slf4j.org>... Mail quota exceeded 554 <dev(a)slf4j.org>... Service unavailable

1 0