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

[Bug 212] New: MessageFormat. format throws Exception when attempting to parse parameters
by bugzilla-daemon＠pixie.qos.ch 13 Mar '13

13 Mar '13

http://bugzilla.slf4j.org/show_bug.cgi?id=212 Summary: MessageFormat.format throws Exception when attempting to parse parameters Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: blocker Priority: P1 Component: jul-to-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: kristof.pelckmans(a)wondergraphs.com I am trying to bridge a LogRecord with a message that is the result of HashMap.toString(): {interface com.google.code.morphia.annotations.Id=(a)com.google.code.morphia.annotations.Id()} and get following exception Caused by: java.lang.IllegalArgumentException: can't parse argument number interface com.google.code.morphia.annotations.Id=(a)com.google.code.morphia.annotations.Id() at java.text.MessageFormat.makeFormat(MessageFormat.java:1339) at java.text.MessageFormat.applyPattern(MessageFormat.java:458) at java.text.MessageFormat.<init>(MessageFormat.java:350) at java.text.MessageFormat.format(MessageFormat.java:811) at org.slf4j.bridge.SLF4JBridgeHandler.getMessageI18N(SLF4JBridgeHandler.java:233) FIX: do not format since there are no parameters! if (params != null && params.length > 0) -- 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 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 269] New: Release osgi-over-slf4j
by bugzilla-daemon＠qos.ch 16 Sep '12

16 Sep '12

http://bugzilla.slf4j.org/show_bug.cgi?id=269 Summary: Release osgi-over-slf4j Product: SLF4J Version: 1.6.x Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: matt(a)thebishops.org The source code for slf4j includes a nice implementation of the OSGi LogService. Could you please package this up and release it? Those of us using OSGi need a Log Service impl that routes to our Logback (or whatever driver) to log messages. Without this package OSGi components that use the Log Service will log out to somewhere else, if at all. Felix' Log Service, for example, is in-memory only. Releasing this existing code would be very beneficial to the OSGi community. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.6-14-g993e6b3
by git-noreply＠pixie.qos.ch 29 Aug '12

29 Aug '12

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 993e6b34079ee96cf188e966ed2fd1f78f4be3d0 (commit) from 0b68150048e745409d0f19463c36c443f7eaf4ae (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=993e6b34079ee96cf188e966ed… http://github.com/ceki/slf4j/commit/993e6b34079ee96cf188e966ed2fd1f78f4be3d0 commit 993e6b34079ee96cf188e966ed2fd1f78f4be3d0 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Aug 29 15:10:47 2012 +0200 remove link to ohloh counter diff --git a/slf4j-site/src/site/pages/templates/footer.js b/slf4j-site/src/site/pages/templates/footer.js index db27372..b6817a9 100644 --- a/slf4j-site/src/site/pages/templates/footer.js +++ b/slf4j-site/src/site/pages/templates/footer.js @@ -4,10 +4,6 @@ document.write('<table class="footer" border="0">') document.write('<tr>') document.write(' <td valign="top" align="left">Copyright © 2004-2012 <a href="http://www.qos.ch/">QOS.ch</a></td>') - -document.write(' <td align="right" rowspan="2">') -document.write(' <script type="text/javascript" src="http://www.ohloh.net/p/11217/widgets/project_users.js"></script>') -document.write(' </td>') document.write('</tr>') AAT = '@' @@ -16,7 +12,6 @@ document.write('<tr>') document.write('<td align="left" colspan="1">') document.write('We are actively looking for volunteers to proofread the documentation. Please send your corrections or suggestions for improvement to "corrections' + AAT +'qos'+DOOTT+'ch". See also the <a href="http://articles.qos.ch/contributing.html">instructions for contributors</a>.'); document.write('</td>') -document.write(' <td> </td>') document.write('</tr>') ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/templates/footer.js | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[qos-ch/slf4j] 993e6b: remove link to ohloh counter
by Ceki Gulcu 29 Aug '12

29 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 993e6b34079ee96cf188e966ed2fd1f78f4be3d0 https://github.com/qos-ch/slf4j/commit/993e6b34079ee96cf188e966ed2fd1f78f4b… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-29 (Wed, 29 Aug 2012) Changed paths: M slf4j-site/src/site/pages/templates/footer.js Log Message: ----------- remove link to ohloh counter

1 0

[GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.6-13-g0b68150
by git-noreply＠pixie.qos.ch 23 Aug '12

23 Aug '12

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 0b68150048e745409d0f19463c36c443f7eaf4ae (commit) from d74da4635bf1bb026c181e816482f8f81825c734 (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=0b68150048e745409d0f19463c… http://github.com/ceki/slf4j/commit/0b68150048e745409d0f19463c36c443f7eaf4ae commit 0b68150048e745409d0f19463c36c443f7eaf4ae Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Aug 23 19:20:23 2012 +0200 docs updates diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html index 6ec99ec..e01c22f 100644 --- a/slf4j-site/src/site/pages/codes.html +++ b/slf4j-site/src/site/pages/codes.html @@ -159,16 +159,59 @@ slf4j-simple-${version}.jar and slf4j-nop-${version}.jar on the class path and you wish to use the nop (no-operation) binding, then remove - slf4j-simple-${version}.jar from the class path. If it is - not possible to remove the superflous bindings, SLF4J will still - bind with one logging framework/implementation. As of version - 1.6.6, SLF4J will name the framework/implementation class it is - actually bound to. - - Note The warning emitted by - SLF4J is just that, a warning. + slf4j-simple-${version}.jar from the class path. + The list of locations that SLF4J provides in this warning + usually provides sufficient information to identify the dependency + transitively pulling in an unwanted SLF4J binding into your + project. In your project's pom.xml file, exclude this SLF4J + binding when declaring the unscrupulous dependency. For example, + cassandra-all version 0.8.1 declares both log4j + and slf4j-log4j12 as compile-time dependencies. Thus, + when you include cassandra-all a dependnecy in your + project, it will pulling in both slf4j-log4j12.jar and + log4j.jar as dependencies. In case you do not wish to use + log4j as the the SLF4J backend, you can instruct Maven to exclude + these two artifacts as shown next: + + <pre class="prettyprint"><dependencies> + <dependency> + <groupId> org.apache.cassandra</groupId> + <artifactId>cassandra-all</artifactId> + <version>0.8.1</version> + + <exclusions> + <exclusion> + <groupId>org.slf4j</groupId> + <artifactId>slf4j-log4j12</artifactId> + </exclusion> + <exclusion> + <groupId>log4j</groupId> + <artifactId>log4j</artifactId> + </exclusion> + </exclusions> + + </dependency> +</dependencies></pre> + + Note The warning emitted by + SLF4J is just that, a warning. Even when multiple bindings are + present, SLF4J will pick one logging framework/implementation and + bind with it. The way SLF4J picks a binding is determined by the + JVM and for all practical purposes should be considered random. As + of version 1.6.6, SLF4J will name the framework/implementation + class it is actually bound to. + + Embedded components such as libraries or frameworks should not + declare a dependency on any SLF4J binding but only depend on + slf4j-api. When a library declares a compile-time dependency on a + SLF4J binding, it imposes that binding on the end-user, thus + negating SLF4J's purpose. When you come across an embedded + component declaring a compile-time dependency on any SLF4J binding, + please take the time to contact the authors of said + component/library and kindly ask them to mend their ways. +  <h3 class="doAnchor" name="version_mismatch">slf4j-api version diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html index b9a07b1..e80021a 100644 --- a/slf4j-site/src/site/pages/faq.html +++ b/slf4j-site/src/site/pages/faq.html @@ -657,7 +657,7 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory jcl-over-slf4j, you would need to exclude commons-logging in all of your project's dependencies which transitively depend on commons-logging. <a - href="http://maven.apache.org/guides/introduction/introduction-to-optional-and-ex…">Dependency + href="http://maven.apache.org/guides/introduction/introduction-to-optional-and-ex…">Dependency exclusion</a> is described in the Maven documentation. Excluding commons-logging explicitly for multiple dependencies distributed on several pom.xml files can be a cumbersome and a diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html index 940a825..ce4b5b6 100644 --- a/slf4j-site/src/site/pages/manual.html +++ b/slf4j-site/src/site/pages/manual.html @@ -248,9 +248,9 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail dependencies for logging</h3> Please note that embedded components such as libraries or - frameworks should not declare a dependency on any slf4j binding - but only on slf4j-api. SLF4J usage in embedded components is - also discussed in the FAQ in relation with <a + frameworks should not declare a dependency on any SLF4J binding + but only depend on slf4j-api. SLF4J usage in embedded + components is also discussed in the FAQ in relation with <a href="faq.html#configure_logging">logging configuration</a>, <a href="faq.html#optional_dependency">dependency reduction</a> and <a href="faq.html#optional_dependency">testing</a>. ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/codes.html | 59 ++++++++++++++++++++++++++++---- slf4j-site/src/site/pages/faq.html | 2 +- slf4j-site/src/site/pages/manual.html | 6 ++-- 3 files changed, 55 insertions(+), 12 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java

1 0

[qos-ch/slf4j] 0b6815: docs updates
by Ceki Gulcu 23 Aug '12

23 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 0b68150048e745409d0f19463c36c443f7eaf4ae https://github.com/qos-ch/slf4j/commit/0b68150048e745409d0f19463c36c443f7ea… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-23 (Thu, 23 Aug 2012) Changed paths: M slf4j-site/src/site/pages/codes.html M slf4j-site/src/site/pages/faq.html M slf4j-site/src/site/pages/manual.html Log Message: ----------- docs updates

1 0

Java 5 wrapper for slf4j
by Russ Jackson 22 Aug '12

22 Aug '12

Hey team, First, thanks for all the hard work and the great capability you provide with slf4j. I recently wrote a simple Java 5 wrapper for slf4j and was hoping that perhaps you would want to add it as a sub-project on your site. I think it will bridge the gap for those folks wanting to use some of the enhanced capabilities of Java 5. I put it on google code last night so I had someplace to share it from and posted a quick blog entry. Here's the link to the blog that will get you to the code: http://usna86-techbits.blogspot.com/2012/08/introducing-slf4j5-logging-vara… Let me know if you guys are interested in picking this up. Thanks. Russ Jackson

1 0

[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