August 2011 - slf4j-dev - mailman3.qos.ch

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-41-gced19de
by git-noreply＠pixie.qos.ch 15 Aug '11

15 Aug '11

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 ced19dedec4206252d911b9c947c439117ee6702 (commit) from e452403419909770f558226c639a7d7e94d1715d (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=ced19dedec4206252d911b9c94… http://github.com/ceki/slf4j/commit/ced19dedec4206252d911b9c947c439117ee6702 commit ced19dedec4206252d911b9c947c439117ee6702 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Aug 15 18:57:38 2011 +0200 - Fix #138 - FAQ entry on the FATAL level now is based on the superiority of markers diff --git a/pom.xml b/pom.xml index 5f688b0..db7496a 100644 --- a/pom.xml +++ b/pom.xml @@ -35,7 +35,7 @@ <modules> <module>slf4j-api</module> - <module>slf4j-scala-api</module> +  <module>slf4j-simple</module> <module>slf4j-nop</module> <module>slf4j-jdk14</module> diff --git a/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java b/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java index c2063f3..49e97fe 100644 --- a/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java +++ b/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java @@ -26,10 +26,7 @@ package org.slf4j; import java.io.IOException; import java.net.URL; -import java.util.ArrayList; -import java.util.Arrays; -import java.util.Enumeration; -import java.util.List; +import java.util.*; import org.slf4j.helpers.NOPLoggerFactory; import org.slf4j.helpers.SubstituteLoggerFactory; @@ -212,15 +209,19 @@ public final class LoggerFactory { paths = loggerFactoryClassLoader .getResources(STATIC_LOGGER_BINDER_PATH); } - List implementationList = new ArrayList(); + // use Set instead of list in order to deal with bug #138 + // LinkedHashSet appropriate here because it preserves insertion order during iteration + Set implementationSet = new LinkedHashSet(); while (paths.hasMoreElements()) { URL path = (URL) paths.nextElement(); - implementationList.add(path); + implementationSet.add(path); } - if (implementationList.size() > 1) { + if (implementationSet.size() > 1) { Util.report("Class path contains multiple SLF4J bindings."); - for (int i = 0; i < implementationList.size(); i++) { - Util.report("Found binding in [" + implementationList.get(i) + "]"); + Iterator iterator = implementationSet.iterator(); + while(iterator.hasNext()) { + URL path = (URL) iterator.next(); + Util.report("Found binding in [" + path + "]"); } Util.report("See " + MULTIPLE_BINDINGS_URL + " for an explanation."); } diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index ef70379..dbae2c6 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -994,38 +994,63 @@ logger.debug("The new entry is {}.", entry);</pre> <dt> <a name="fatal" href="#fatal"> Why doesn't the - <code>org.slf4j.Logger</code> interface have methods for the FATAL - level? </a> + <code>org.slf4j.Logger</code> interface have methods for the + FATAL level? </a> </dt> <dd> - From the stand point of a logging system, the distinction - between a fatal error and an error is usually not very - useful. Most programmers exit the application when a fatal - error is encountered. However, a logging library cannot (and - should not) decide on its own to terminate an - application. The initiative to exit the application must be - left to the developer. + The <a href="apidocs/org/slf4j/Marker.html">Marker</a> + interface, part of the <code>org.slf4j</code> package, renders + the FATAL level largely redundant. If a given error requires + attention beyond that allocated for ordinary errors, simply mark + the logging statement with a specially designated marker which + can be named "FATAL" or any other name to your liking. - - - Thus, the most the FATAL level can do is to - highlight a given error as the cause for - application to crash. However, errors are by definition - exceptional events that merit attention. If a given - situation causes errors to be logged, the causes should be - attended to as soon as possible. However, if the "error" is - actually a normal situation which cannot be prevented but - merits being aware of, then it should be marked as WARN, not - ERROR. + + Here is an example, + +<pre class="prettyprint">import org.slf4j.Logger; +import org.slf4j.LoggerFactory; +import org.slf4j.Marker; +import org.slf4j.MarkerFactory; + +class Bar { + void foo() { + Marker fatal = MarkerFactory.getMarker("FATAL"); + Logger logger = LoggerFactory.getLogger("aLogger"); + + try { + ... obtain a JDBC connection + } catch (JDBException e) { + logger.error(fatal, "Failed to obtain JDBC connection", e); + } + } +}</pre> + + + While markers are part of the SLF4J API, only logback + supports markers off the shelf. For example, if you add the + <code>%marker</code> conversion word to its pattern, logback's + <code>PatternLayout</code> will add marker data to its + output. Marker data can be used to <a + href="http://logback.qos.ch/manual/filters.html">filter + messages</a> or even <a + href="http://logback.qos.ch/manual/appenders.html#OnMarkerEvaluator">trigger</a> + an outgoing email <a + href="http://logback.qos.ch/recipes/emailPerTransaction.html">at + the end of an individual transaction</a>. - - Assuming the ERROR level designates exceptional situations - meriting close attention, we are inclined to believe that the - FATAL level is superfluous. + + In combination with logging frameworks such as log4j and + java.util.logging which do not support markers, marker data will + be silently ignored. + + Markers add a new dimension with infinite possible values for + processing log statements compared to five values, namely ERROR, + WARN, INFO, DEBUG and TRACE, allowed by levels. At present time, + only logback supports marker data. However, nothing prevents + other logging frameworks from making use of marker data. - - <hr /> </dd> diff --git a/slf4j-site/src/site/pages/news.html b/slf4j-site/src/site/pages/news.html index a60a10e..55c91f5 100644 --- a/slf4j-site/src/site/pages/news.html +++ b/slf4j-site/src/site/pages/news.html @@ -29,7 +29,14 @@ <hr noshade="noshade" size="1"/> - <h3>, 2011 - Release of SLF4J 1.6.2</h3> + <h3>August xth, 2011 - Release of SLF4J 1.6.2</h3> + + + Fixed <a + href="http://bugzilla.slf4j.org/show_bug.cgi?id=138">bug + #138</a>. SLF4J will no longer complain about multiple SLF4J + bindings when running under a Weblogic server. + Added certain missing classes to the log4j-over-slf4j module as requested in <a ----------------------------------------------------------------------- Summary of changes: pom.xml | 2 +- .../src/main/java/org/slf4j/LoggerFactory.java | 19 +++--- slf4j-site/src/site/pages/faq.html | 77 +++++++++++++------- slf4j-site/src/site/pages/news.html | 9 ++- 4 files changed, 70 insertions(+), 37 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[Bug 233] New: Improve unsupported operations in bridges
by bugzilla-daemon＠pixie.qos.ch 15 Aug '11

15 Aug '11

http://bugzilla.slf4j.org/show_bug.cgi?id=233 Summary: Improve unsupported operations in bridges Product: SLF4J Version: 1.6.x Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: laurent.pellegrino(a)gmail.com I tried to use log4j-over-slf4j in a legacy project that provides its own LoggerFactory and when I use log4j-over-slf4j I get for example a java.lang.NoSuchMethodError for Logger getLogger(String name, LoggerFactory factory). Indeed, it seems that log4j-over-slf4j does no support this method. However, I think it would be nice to provide all the methods that are exposed by the public log4j API and to throw for example an exception like an UnsupportedOperationException (with a description message) when the method is not yet implemented. First, to know (with a clear message) that the bridge does not support these methods without having to check into the source code in order to see whether the method is provided or not. But also to help the developers to know what are the methods they have to implement without making a diff between the log4j and the log4j-over-slf4j source code. Maybe this concept can be applied for all the bridge. -- 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

A problem with Oracle !!!
by mostafa elbehery 15 Aug '11

15 Aug '11

Dears, I was using Logback.xml configuration during implementing " Loggings " via " SLF4J ", when I faced this problem ... Although I used " DBAppender " before and it was working fine, this time its not at all ... I tried to detect where is the error by the following ways but I could not :- 1 - I added " FileAppender " on the same " backlog.xml ", and it was working fine, while " DBAppender " is not ...2 - I replaced the ORACLE configuration with MYSQL configuration and it worked perfectly !!!! 3 - I replaced the MySql configuration of another working & tested project with Oracle Configuration and it did not work too ... I attached the " backlog.xml " with ORACLE configuration and willing to find help ... Thanks & Regards ...

1 0

log4j-over-slf4j
by Laurent Pellegrino 15 Aug '11

15 Aug '11

Hi all, I have tried to use the log4j-over-slf4j bridge and there are some classes that are not included into the bridge (version 1.6.1 from Maven Central) such as org.apache.log4j.spi.LoggerFactory. However after looking at the development version from https://github.com/ceki/slf4j/tree/master/log4j-over-slf4j/src/main/java/or…, it seems that now several classes are bundled with the bridge. Unfortunately this version (which is around 10 months old) is not available from Maven Central. Do you intend to perform a release soon? Is there a snapshots repository available? Kind Regards, Laurent

2 2

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-40-ge452403
by git-noreply＠pixie.qos.ch 14 Aug '11

14 Aug '11

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 e452403419909770f558226c639a7d7e94d1715d (commit) from 429571715ba5ca59a1945deca877891c393bfe10 (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=e452403419909770f558226c63… http://github.com/ceki/slf4j/commit/e452403419909770f558226c639a7d7e94d1715d commit e452403419909770f558226c639a7d7e94d1715d Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sun Aug 14 22:29:10 2011 +0200 illustrate slf4j binding and bridging diff --git a/slf4j-site/src/site/images.src/concrete-bindings.odg b/slf4j-site/src/site/images.src/concrete-bindings.odg new file mode 100644 index 0000000..f45c037 Binary files /dev/null and b/slf4j-site/src/site/images.src/concrete-bindings.odg differ diff --git a/slf4j-site/src/site/images.src/legacy.odg b/slf4j-site/src/site/images.src/legacy.odg new file mode 100644 index 0000000..e25ae82 Binary files /dev/null and b/slf4j-site/src/site/images.src/legacy.odg differ diff --git a/slf4j-site/src/site/resources/images/concrete-bindings.png b/slf4j-site/src/site/resources/images/concrete-bindings.png new file mode 100644 index 0000000..44ff261 Binary files /dev/null and b/slf4j-site/src/site/resources/images/concrete-bindings.png differ diff --git a/slf4j-site/src/site/resources/images/legacy.png b/slf4j-site/src/site/resources/images/legacy.png new file mode 100644 index 0000000..498097b Binary files /dev/null and b/slf4j-site/src/site/resources/images/legacy.png differ ----------------------------------------------------------------------- Summary of changes: .../src/site/images.src/concrete-bindings.odg | Bin 0 -> 23253 bytes slf4j-site/src/site/images.src/legacy.odg | Bin 0 -> 23714 bytes .../site/resources/images/concrete-bindings.png | Bin 0 -> 122493 bytes slf4j-site/src/site/resources/images/legacy.png | Bin 0 -> 180161 bytes 4 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 slf4j-site/src/site/images.src/concrete-bindings.odg create mode 100644 slf4j-site/src/site/images.src/legacy.odg create mode 100644 slf4j-site/src/site/resources/images/concrete-bindings.png create mode 100644 slf4j-site/src/site/resources/images/legacy.png hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[Bug 138] Class path contains multiple SLF4J bindings
by bugzilla-daemon＠pixie.qos.ch 12 Aug '11

12 Aug '11

http://bugzilla.slf4j.org/show_bug.cgi?id=138 --- Comment #23 from tom_1st <tvtreeck(a)nepatec.de> 2011-08-12 15:00:54 CEST --- Come on guys - there is a solution including a patch, plus lots of people supporting/commenting it - what's the problem? Why isn't it fixed? -- 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 232] New: SLF4j not logging Debug logs with java Util log bindings .
by bugzilla-daemon＠pixie.qos.ch 10 Aug '11

10 Aug '11

http://bugzilla.slf4j.org/show_bug.cgi?id=232 Summary: SLF4j not logging Debug logs with java Util log bindings . Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: shrey4bskyb(a)googlemail.com Created attachment 80 --> http://bugzilla.slf4j.org/attachment.cgi?id=80 Test Project to repoduce the issue Log statements with Debug and Trace levels are missing inspite of setting logging level for java.util.logging to ALL . Issue occures when java utill logging is set as bindings . Attached is a test project to reproduce the problem . -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-39-g4295717
by git-noreply＠pixie.qos.ch 09 Aug '11

09 Aug '11

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 429571715ba5ca59a1945deca877891c393bfe10 (commit) from 96424540713b1288aae121c459f25dc66134f346 (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=429571715ba5ca59a1945deca8… http://github.com/ceki/slf4j/commit/429571715ba5ca59a1945deca877891c393bfe10 commit 429571715ba5ca59a1945deca877891c393bfe10 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Aug 9 16:59:11 2011 +0200 alphabetical ordering diff --git a/slf4j-site/src/site/pages/index.html b/slf4j-site/src/site/pages/index.html index d1973bb..75a6933 100644 --- a/slf4j-site/src/site/pages/index.html +++ b/slf4j-site/src/site/pages/index.html @@ -141,15 +141,15 @@ <li><a href="http://code.google.com/p/openmeetings/">OpenMeetings</a></li> <li><a href="http://www.openrdf.org/">OpenRDF</a></li> <li><a href="http://docs.safehaus.org/display/PENROSE/Home">Penrose</a></li> - <li><a href="http://sonar.codehaus.org/">Sonar</a></li> <li><a href="http://pzfilereader.sourceforge.net/">PZFileReader</a></li> + <li><a href="http://www.quartz-scheduler.org/">Quartz Scheduler</a></li> </ul> </td> <td valign="top"> <ul> - <li><a href="http://www.quartz-scheduler.org/">Quartz Scheduler</a></li> <li><a href="http://www.quickfixj.org/">QuickFIX/J</a></li> + <li><a href="http://sonar.codehaus.org/">Sonar</a></li> <li><a href="http://smsj.sourceforge.net/dependencies.html">SMSJ</a></li> <li><a href="http://www.springframework.org/osgi">Spring-OSGi</a></li> <li><a href="http://static.springsource.org/s2-dmserver/2.0.x/user-guide/htmlsingle/user…">SpringSource dm Server™</a></li> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/index.html | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-38-g9642454
by git-noreply＠pixie.qos.ch 09 Aug '11

09 Aug '11

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 96424540713b1288aae121c459f25dc66134f346 (commit) via 110d27b67e44b4094cd4b1ecdd42f3f30d3b339b (commit) from 9d0543fb6bec03e09582e8255425dacfb9f4ec39 (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=96424540713b1288aae121c459… http://github.com/ceki/slf4j/commit/96424540713b1288aae121c459f25dc66134f346 commit 96424540713b1288aae121c459f25dc66134f346 Merge: 110d27b 9d0543f Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Aug 9 16:52:37 2011 +0200 Merge branch 'master' of git.qos.ch:slf4j http://git.qos.ch/gitweb/?p=slf4j.git;a=commit;h=110d27b67e44b4094cd4b1ecdd… http://github.com/ceki/slf4j/commit/110d27b67e44b4094cd4b1ecdd42f3f30d3b339b commit 110d27b67e44b4094cd4b1ecdd42f3f30d3b339b Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Aug 9 16:52:21 2011 +0200 added xwiki to the list og projects using slf4j diff --git a/slf4j-site/src/site/pages/index.html b/slf4j-site/src/site/pages/index.html index 7f9571d..d1973bb 100644 --- a/slf4j-site/src/site/pages/index.html +++ b/slf4j-site/src/site/pages/index.html @@ -142,12 +142,12 @@ <li><a href="http://www.openrdf.org/">OpenRDF</a></li> <li><a href="http://docs.safehaus.org/display/PENROSE/Home">Penrose</a></li> <li><a href="http://sonar.codehaus.org/">Sonar</a></li> + <li><a href="http://pzfilereader.sourceforge.net/">PZFileReader</a></li> </ul> </td> <td valign="top"> <ul> - <li><a href="http://pzfilereader.sourceforge.net/">PZFileReader</a></li> <li><a href="http://www.quartz-scheduler.org/">Quartz Scheduler</a></li> <li><a href="http://www.quickfixj.org/">QuickFIX/J</a></li> <li><a href="http://smsj.sourceforge.net/dependencies.html">SMSJ</a></li> @@ -158,6 +158,7 @@ <li><a href="http://www.wtfigo.org/index.html">WTFIGO</a></li> <li><a href="http://yaslibrary.sourceforge.net/index.shtml">YASL</a></li> <li><a href="http://xooctory.xoocode.org/">Xooctory</a></li> + <li><a href="http://xwiki.org">XWiki</a></li> </ul> </td> </tr> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/index.html | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[Bug 231] New: Allow completely turning off logging for production environments
by bugzilla-daemon＠pixie.qos.ch 08 Aug '11

08 Aug '11

http://bugzilla.slf4j.org/show_bug.cgi?id=231 Summary: Allow completely turning off logging for production environments Product: SLF4J Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P1 Component: slf4j-android AssignedTo: slf4j-dev(a)qos.ch ReportedBy: thorsten.Moeller(a)unibas.ch The SLF4J Android port should provide means to completely turn of logging (for performance reasons, for production use). This issue is intended primarily for discussing the different options for a solution. There are at least three ways how it could be achieved: First, by deactivating all logging related method calls when compiling an application. Obviously, this would be tedious if done manually and should therefore be automated by some kind of scripting and be part of the build process. Second, by a "null" logger implementation that can be used instead of the standard one (which delegates to Android Log). The downside here is that logging is not entirely deactivated since the application code is compiled unchanged, hence, there is still (more or less) logging overhead. Also, the question is how should we switch between the two: programmatically or externally configurable? A third option is to distribute two different JARs, one for debugging purposes, another one for production use. The difference between the two JARs is that the former contains the standard logger, while the latter contains a null logger. This would be easily integratable in a Maven-managed build process: one can define two profiles, say "dev" and "rel". The latter would define a dependency using a classifier referring to the null-logger JAR whereas the former would define a dependency to the JAR containing the default logger. However, this approach has the same downside than the second one. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1