[slf4j-dev] svn commit: r1350 - in slf4j/trunk/slf4j-site/src/site/pages: . css
ceki at slf4j.org
ceki at slf4j.org
Wed Jun 10 20:21:01 CEST 2009
Author: ceki
Date: Wed Jun 10 20:21:01 2009
New Revision: 1350
Modified:
slf4j/trunk/slf4j-site/src/site/pages/codes.html
slf4j/trunk/slf4j-site/src/site/pages/compatibility.html
slf4j/trunk/slf4j-site/src/site/pages/css/site.css
slf4j/trunk/slf4j-site/src/site/pages/manual.html
slf4j/trunk/slf4j-site/src/site/pages/news.html
Log:
- added error code for "Multiple Bindings"
- added a compatibility report on 1.5.7
- minor fix in site.css
- paragraph reordering in manual.html
- updated news.html
Modified: slf4j/trunk/slf4j-site/src/site/pages/codes.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/codes.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/codes.html Wed Jun 10 20:21:01 2009
@@ -100,6 +100,7 @@
<p>You can download SLF4J bindings from the project <a
href="http://www.slf4j.org/download.html">download page</a>. </p>
+ <!-- ====================================================== -->
<h3>
<a name="illegalAccess" href="">java.lang.IllegalAccessError: tried to access field
org.slf4j.impl.StaticLoggerBinder.SINGLETON from class
@@ -126,6 +127,31 @@
href="faq.html#compatibility">FAQ entry</a>.
</p>
+ <!-- ====================================================== -->
+ <h3>
+ <a name="multiple_bindings" href="#multiple_bindings">Multiple
+ bindings were found on the class path</a>
+ </h3>
+
+
+ <p>SLF4J API is desinged to bind with one and only one underlying
+ logging framework at a time. If more than one binding is present
+ on the class path, SLF4J will emit a warning, listing the location
+ of those bindings. When this happens, select the one and only one
+ binding you wish to use, and remove the other bindings.
+ </p>
+
+ <p>For example, if you have both
+ <em>slf4j-simple-${version}.jar</em> and
+ <em>slf4j-nop-${version}.jar</em> on the class path and you wish
+ to use the nop (no-operation) binding, then remove
+ <em>slf4j-simple-${version}.jar</em> from the class parh.</p>
+
+
+
+
+
+ <!-- ====================================================== -->
<h3>
<a name="null_LF" href="#null_LF">Logging factory implementation
cannot be null</a>
Modified: slf4j/trunk/slf4j-site/src/site/pages/compatibility.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/compatibility.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/compatibility.html Wed Jun 10 20:21:01 2009
@@ -42,6 +42,10 @@
to suspect incompatible changes not mentioned here, please kindly
contact the slf4j developers list.</p>
+ <h2><a href="#1_5_7" name="1_5_6">Version 1.5.7 compared to 1.5.6</a></h2>
+
+ <p>No breaking changes to report.</p>
+
<h2><a href="#1_5_6" name="1_5_5">Version 1.5.6 compared to 1.5.5</a></h2>
Modified: slf4j/trunk/slf4j-site/src/site/pages/css/site.css
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/css/site.css (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/css/site.css Wed Jun 10 20:21:01 2009
@@ -82,9 +82,9 @@
h4 {
padding-top:5px;
- background-color: transparent;
- font-weight: large;
- font-size: normal;
+ background-color: transparent;
+ font-weight: normal;
+ font-size: large;
}
table.footer {
Modified: slf4j/trunk/slf4j-site/src/site/pages/manual.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/manual.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/manual.html Wed Jun 10 20:21:01 2009
@@ -210,14 +210,20 @@
approach has proven to be simple and very robust.
</p>
- <p>Those unfortunate to have to use one or more unchangable
- legacy components which use log4j, Jakarta Commons Logging or JDK 1.4
- logging directly, may have to use the slf4j drop-in replacements
- which map these direct calls to slf4j. See the
- <a href="legacy.html">Briding legacy APIs</a> page for
- details.</p>
+ <h3><a name="consolidate" href="#consolidate">Consolidate
+ logging via SLF4J</a></h3>
+ <p>Often times, a given project will depend on various
+ components which rely on logging APIs other than SLF4J. It is
+ common to find projects depending on a combination of JCL,
+ java.util.logging, log4j and SLF4J. It then becomes desirable to
+ consolidate logging through a single channel. SLF4J caters for
+ this common use-case by providing bridging modules for JCL,
+ java.util.logging and log4j. For more details, please refer to
+ the page on <a href="legacy.html"><b>Bridging legacy
+ APIs</b></a>.
+ </p>
<h3><a name="mdc" href="#mdc">Mapped Diagnostic Context (MDC)
support</a></h3>
@@ -245,18 +251,7 @@
in the logback manual.
</p>
- <h3><a name="consolidate" href="#consolidate">Consolidate
- logging via SLF4J</a></h3>
-
- <p>Often times, a given project will depend on various
- components which rely on logging APIs other than SLF4J. It is
- common to find projects depending on JCL, java.util.logging,
- log4j and SLF4J at the same time. It then becomes desirable to
- consolidate logging through a single channel. SLF4J caters for
- this common use-case by providing bridging modules for JCL,
- java.util.logging and log4j. For more details, please refer to
- the page on <a href="legacy.html">Bridging legacy APIs</a>.
- </p>
+
<h3><a name="summary" href="#summary">Executive
summary</a>
Modified: slf4j/trunk/slf4j-site/src/site/pages/news.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/news.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/news.html Wed Jun 10 20:21:01 2009
@@ -27,8 +27,16 @@
<hr noshade="noshade" size="1"/>
- <h3>April x, 2009 - Release of SLF4J 1.5.7</h3>
+ <h3>June 10th, 2009 - Release of SLF4J 1.5.7</h3>
+ <p>SLF4J version 1.5.7 consist of bug fixes and minor
+ enhancements. It is totally compatible with SLF4J version 1.5.6.</p>
+
+ <p>SLF4J will now emit a warning if more than one binding is present
+ on the class path. This enhancement was proposed in <a
+ href="http://bugzilla.slf4j.org/show_bug.cgi?id=132">bug 132</a>
+ contributed by by Robert Elliot.
+ </p>
<p>The Log interface implementations in the jcl-over-slf4j module
will now correctly cope with serialization. This fixes <a
@@ -49,6 +57,13 @@
reported by Pepijn Van Eeckhoudt and independently by Dan Lewis.
</p>
+ <p>In case the <code>toString()</code> method of a parameter throws
+ an exception, <code>MessageFormatter</code> will now print an error
+ message, instead of letting the exception bubble higher up as
+ previously. This fixes <a
+ href="http://bugzilla.slf4j.org/show_bug.cgi?id=112">bug 112</a>
+ submitted by Joern Huxhorn.
+ </p>
<hr noshade="noshade" size="1"/>
More information about the slf4j-dev
mailing list