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

[Bug 236] New: Use standard java.util.ServiceLoader for SLF4J Binding
by bugzilla-daemon＠pixie.qos.ch 25 Feb '13

25 Feb '13

http://bugzilla.slf4j.org/show_bug.cgi?id=236 Summary: Use standard java.util.ServiceLoader for SLF4J Binding Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cronier.jy(a)gmail.com What about use ServiceLoader to find which binding to use? For JDK<1.6 compatibility, we can test Class.forName("java.util.ServiceLoader") and switch to an internal equivalent implementation of ServiceLoader. No need to have one (or multiple) StaticLoggerBinder. This ServiceLoader is used, for example, for JRE XSL implementation, or java.sql.Driver. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 10

[Bug 218] New: Broken link on website
by bugzilla-daemon＠pixie.qos.ch 21 Sep '12

21 Sep '12

http://bugzilla.slf4j.org/show_bug.cgi?id=218 Summary: Broken link on website Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cowwoc(a)bbs.darktech.org The nabble links found at http://www.slf4j.org/mailing-lists.html point to deleted forums. Please recreate the forums. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 1

[Bug 220] New: Cannot build slf4j from source - missing osgi-build.xml
by bugzilla-daemon＠pixie.qos.ch 09 Aug '12

09 Aug '12

http://bugzilla.slf4j.org/show_bug.cgi?id=220 Summary: Cannot build slf4j from source - missing osgi-build.xml Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: dick.jones(a)kinetx.com I tried to build slf4j 1.6.1 from source and the build failed with the following error: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.2:run (ant-osgi-test) on project integration: An Ant BuildException has occured: The following error occurred while executing this line: java.io.FileNotFoundException: C:\Users\dick.jones.KINETX\Downloads\slf4j-1.6.1\integration\osgi-build.xml (The system cannot find the file specified) I emailed Ceki Gulcu who said the file, osgi-build.xml, was inadvertently ommitted and asked that I enter this as a bug. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 1

[Bug 186] New: [patch] Enhanced SimpleLogger implementation
by bugzilla-daemon＠pixie.qos.ch 12 Jun '12

12 Jun '12

http://bugzilla.slf4j.org/show_bug.cgi?id=186 Summary: [patch] Enhanced SimpleLogger implementation Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cedrik.lime(a)gmail.com Created an attachment (id=70) --> (http://bugzilla.slf4j.org/attachment.cgi?id=70) New implementation of SimpleLogger I recently had to enhance SimpleLogger by back-porting some functionalities of commons-logging's SimpleLog into it. Namely, I have added the following: * optional configuration file; if none found, you get the exact same set of features as the currently released SimpleLogger. * enable to log more than the info log level * enable to set different log levels for different Loggers * enable to show/hide thread name * very primitive log messages customisation (about the same as commons-logging) Once again, the new code is totally compatible in behaviour and output with the currently released SimpleLogger. I also made it so that current users of commons-logging can upgrade to SLF4J very easily. Finally, I made sure to keep SimpleLogger as simple as possible: we already have fully-fledged logging frameworks, let's not re-invent one! I think this new implementation would enhance the value of SLF4J, while keeping a perfect retro-compatibility with previous versions. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 11

[Bug 234] New: log4j-over-slf4j and legacy projects providing their own log4j LoggerFactory
by bugzilla-daemon＠pixie.qos.ch 04 Jun '12

04 Jun '12

http://bugzilla.slf4j.org/show_bug.cgi?id=234 Summary: log4j-over-slf4j and legacy projects providing their own log4j LoggerFactory Product: SLF4J Version: 1.6.x Platform: All OS/Version: All Status: NEW Severity: blocker 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 a java.lang.NoSuchMethodError for Logger#getLogger(String name, LoggerFactory factory). After having inspected the log4j-over-slf4j source code, it seems that the bridge does not provide an implementation for the Logger#getLogger(String name, LoggerFactory factory) method. Is there any reason for that? -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 5

[Bug 219] New: Typo in error message
by bugzilla-daemon＠pixie.qos.ch 19 Apr '12

19 Apr '12

http://bugzilla.slf4j.org/show_bug.cgi?id=219 Summary: Typo in error message Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows NT Status: NEW Severity: blocker Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: cowwoc(a)bbs.darktech.org Replace "becasue" with "because" across the slf4j code-base. I got this specific error message: SLF4J: The following loggers will not work becasue they were created SLF4J: during the default configuration phase of the underlying logging system. SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 2

org.slf4j.NDC implementation problem
by Antony Bowesman 23 Nov '11

23 Nov '11

I'm migrating a log4j environment to SLF4J. Our log4j usage makes use of NDC as a small stack and I'm using the ext package to use the slf4j NDC. However, the problem is that the NDC implementation just sits on top of MDC and the MDC context is inherited by threads, whereas NDC is NOT, unless inherit() is called specifically. I then went to patch my NDC usage to call NDC.clear(), but the org.slf4j.NDC does not expose it. This means the log output contains the NDC context from my root thread and there's no way to clear any of the context. So, I have patched NDC as attached. Is there any reason why this cannot be taken to the core code? Antony

2 2

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-2-g3a46131
by git-noreply＠pixie.qos.ch 12 Nov '11

12 Nov '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 3a461317916651390d83891d3d4b73d9e38dcb28 (commit) from ccd1c8355b9ed6c77b375d7efd459416f10fb62e (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=3a461317916651390d83891d3d… http://github.com/ceki/slf4j/commit/3a461317916651390d83891d3d4b73d9e38dcb28 commit 3a461317916651390d83891d3d4b73d9e38dcb28 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Nov 12 16:12:16 2011 +0100 docs on version 99 diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index b226ac4..afec6fd 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -78,7 +78,7 @@ </li> <li> - <a href="#maven2">What about Maven 2 transitive + <a href="#maven2">What about Maven transitive dependencies? </a> </li> @@ -609,18 +609,19 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory  - <dt><a name="maven2" href="#maven2">What about Maven2 + <dt><a name="maven2" href="#maven2">What about Maven transitive dependencies? </a> </dt> <dd> - As an author of a library built with Maven2, you might - want to test your application using a binding, say - slf4j-log4j12 or logback-classic, without forcing log4j or - logback-classic as a dependency upon your users. As of SLF4J - version 1.3, this quite easy to accomplish. But first, since - your library's code depends on the SLF4J API you will need to - declare slf4j-api as a compile-time (default scope) + As an author of a library built with Maven, you might want to + test your application using a binding, say slf4j-log4j12 or + logback-classic, without forcing log4j or logback-classic as a + dependency upon your users. This is rather easy to accomplish. + + + Given that your library's code depends on the SLF4J API, you + will need to declare slf4j-api as a compile-time (default scope) dependency. <pre class="prettyprint source"><dependency> @@ -662,18 +663,20 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory </dt> <dd> + alternative 1) explicit exlusion + Many software projects using Maven declare commons-logging as a dependency. Thus, if you wish to migrate to SLF4J or use - jcl-over-slf4j, you would need to declare a commons-logging - exclusion in all of your dependencies which transitively depend - on commons-logging. This can be an error prone process. To - alleviate the pain, Erik van Oosten has developed a <a - href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-n…">clever - hack around this problem.</a> + jcl-over-slf4j, you would need to exclude commons-logging in all + of your project's dependencies which transitively depend on + commons-logging. Excluding commons-logging explicitly can be a + cumbersome and an error prone process. - Alternatively, commons-logging can be rather simply and - conveniently excluded as a dependency by declaring it in the + alternative 2) provided scope + + Commons-logging can be rather simply and conveniently + excluded as a dependency by declaring it in the provided scope within the pom.xml file of your project. The actual commons-logging classes would be provided by jcl-over-slf4j. This translates into the following pom file @@ -700,6 +703,66 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory true. + Unfortunately, while declaring commons-logging in the + provided scope gets the job done, your IDE, e.g. Eclipse, will + still place commons-logging.jar on your projet's class + path as seen by your IDE. You would need to make sure that + jcl-over-slf4j.jar is visible before + commons-logging.jar by your IDE. + + + alternative 3) empty artifacts + + An alternative approach is to depend on an empty + commons-logging.jar artifact. This clever <a + href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-n…">approach + was imagined</a> imagined and initially supported by Erik van + Oosten. + + + The empty artifact is available from a <a + href="http://version99.qos.ch">http://version99.qos.ch</a> a + highly available Maven repository, replicated by several hosts + located in different geographical regions. The following + decleration adds the version99 repository to the set of remote + repositories searched by Maven. + + + <pre class="prettyprint source"><repositories> + <repository> + <id>version99</id> +  + <url>http://version99.qos.ch/</url> + </repository> +</repositories></pre> + + Once you declare version 99-empty of commons-logging in the + <code><dependencyManagement></code> section of your project, + all transtive dependencies for commons-logging will also use + version 99-empty, thus nicely addressing the commons-logging + exclusion problem. + + +<pre class="prettyprint source"><dependencyManagement> + <dependency> + <groupId>commons-logging</groupId> + <artifactId>commons-logging</artifactId> + <version>99-empty</version> + </dependency> + ... other declarations... +</dependencyManagement> + + +<dependencies> + <dependency> + <groupId>org.slf4j</groupId> + <artifactId>jcl-over-slf4j</artifactId> + <version>${project.version}</version> + </dependency> +<dependencies> +</pre> + + </dd> ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/faq.html | 97 +++++++++++++++++++++++++++++------ 1 files changed, 80 insertions(+), 17 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

version 99
by ceki 12 Nov '11

12 Nov '11

Hello all, Building on Erik van Oosten's version99-does-not exist, I've created a highly-available repository serving empty commons-logging and log4j artifacts. Here are the docs, http://www.slf4j.org/faq.html#excludingJCL Your comments are welcome, -- Ceki http://twitter.com/#!/ceki

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-1-gccd1c83
by git-noreply＠pixie.qos.ch 07 Nov '11

07 Nov '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 ccd1c8355b9ed6c77b375d7efd459416f10fb62e (commit) from 38915dafe04496b42ec65732c9376aa26b3c81e9 (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=ccd1c8355b9ed6c77b375d7efd… http://github.com/ceki/slf4j/commit/ccd1c8355b9ed6c77b375d7efd459416f10fb62e commit ccd1c8355b9ed6c77b375d7efd459416f10fb62e Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Nov 7 19:40:22 2011 +0100 improved javadocs diff --git a/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java b/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java index b440a56..5177f24 100644 --- a/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java +++ b/slf4j-api/src/main/java/org/slf4j/spi/LocationAwareLogger.java @@ -30,10 +30,10 @@ import org.slf4j.Marker; /** * An optional interface helping integration with logging systems capable of * extracting location information. This interface is mainly used by SLF4J bridges - * such as jcl104-over-slf4j which need to provide hints so that the underlying logging - * system can extract the correct location information (method name, line number, etc.). - * - * + * such as jcl-over-slf4j, jul-to-slf4j and log4j-over-slf4j or {@link Logger} wrappers + * which need to provide hints so that the underlying logging system can extract + * the correct location information (method name, line number). + * * @author Ceki Gulcu * @since 1.3 */ @@ -49,11 +49,12 @@ public interface LocationAwareLogger extends Logger { /** * Printing method with support for location information. * - * @param marker - * @param fqcn The fully qualified class name of the caller - * @param level - * @param message - * @param t + * @param marker The marker to be used for this event, may be null. + * @param fqcn The fully qualified class name of the logger instance, + * typically the logger class, logger bridge or a logger wrapper. + * @param level One of the level integers defined in this interface + * @param message The message for the log event + * @param t Throwable associated with the log event, may be null. */ public void log(Marker marker, String fqcn, int level, String message, Object[] argArray, Throwable t); ----------------------------------------------------------------------- Summary of changes: .../java/org/slf4j/spi/LocationAwareLogger.java | 19 ++++++++++--------- 1 files changed, 10 insertions(+), 9 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0