[slf4j-dev] [GIT] SLF4J: Simple Logging Facade for Java branch master updated. v_1.6.4-19-g6c7091b

Gitbot git-noreply at pixie.qos.ch
Fri Jun 1 23:57:43 CEST 2012


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  6c7091b3e8c6e66771db9a85f3847b0115c75592 (commit)
      from  dc6d3a03f85d13a01d94f6ce01475ec66dd0b47f (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=6c7091b3e8c6e66771db9a85f3847b0115c75592
http://github.com/ceki/slf4j/commit/6c7091b3e8c6e66771db9a85f3847b0115c75592

commit 6c7091b3e8c6e66771db9a85f3847b0115c75592
Author: Ceki Gulcu <ceki at qos.ch>
Date:   Fri Jun 1 23:56:14 2012 +0200

    duplicate explanation binary compatibility in the manual

diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html
index ba5bd00..08212ff 100644
--- a/slf4j-site/src/site/pages/codes.html
+++ b/slf4j-site/src/site/pages/codes.html
@@ -172,7 +172,7 @@
     <p>An SLF4J binding designates an artifact such as
     <em>slf4j-jdk14.jar</em> or <em>slf4j-log4j12.jar</em> used to
     <em>bind</em> slf4j to an underlying logging framework, say,
-    java.util.logging or log4j.
+    java.util.logging and respectively log4j.
     </p>
 
     <p>Mixing mixing different versions of <em>slf4j-api.jar</em> and
diff --git a/slf4j-site/src/site/pages/css/site.css b/slf4j-site/src/site/pages/css/site.css
index def6249..e06b47e 100644
--- a/slf4j-site/src/site/pages/css/site.css
+++ b/slf4j-site/src/site/pages/css/site.css
@@ -249,21 +249,27 @@ code {
   border: 1px solid black;
   font-family: Arial, sans-serif;	
 }
-
 .highlight {
-  width: 300px;
+  width: 18em;
   float: right;	
   display: inline;
-  font-weight: bolder;
-  border:1px solid #000;
-  background:#FFCC99;	
-  padding-top: 0px;
+  font-size: 110%;
+
+  border: 2px solid #711;
+  -webkit-border-radius: 4px;
+  -moz-border-radius: 4px;
+  border-radius: 4px;
+  background:#FFE0B0;	
+  padding-top: 1ex;
   padding-left: 1ex;
   padding-right: 1ex;
-  margin-left: 3em;
-  margin-right: 3em;
+  padding-bottom: 1ex;
+  margin-left: 1em;
+  margin-right: 0em;
+  margin-bottom: 1ex;
 }
 
+
 .survey { 
   font-weight: bolder;
   font-size: larger;  
diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html
index df7aba4..640629a 100644
--- a/slf4j-site/src/site/pages/manual.html
+++ b/slf4j-site/src/site/pages/manual.html
@@ -246,6 +246,49 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
       corresponding to the logging framework chosen by her.
       </p>
 
+      <h3><a name="compatibility" href="#compatibility">Binary
+      compatibility</a></h3>
+
+      <p>An SLF4J binding designates an artifact such as
+      <em>slf4j-jdk14.jar</em> or <em>slf4j-log4j12.jar</em> used to
+      <em>bind</em> slf4j to an underlying logging framework, say,
+      java.util.logging and respectively log4j.
+      </p>
+
+      <p class="highlight">From the client's perspective all versions
+      of slf4j-api are compatible.  Client code compiled with
+      slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for
+      any N and M. You only need to ensure that the version of your
+      binding matches that of the slf4j-api.jar. You do not have to
+      worry about the version of slf4j-api.jar used by a given
+      dependendency in your project. </p>
+      
+
+      <p>Mixing mixing different versions of <em>slf4j-api.jar</em>
+      and SLF4J binding can cause problems. For example, if you are
+      using slf4j-api-${project.version}.jar, then you should also use
+      slf4j-simple-${project.version}.jar, using
+      slf4j-simple-1.5.5.jar will not work.</p>
+
+     
+      From the client's perspective all versions of slf4j-api are
+      compatible. Client code compiled with <em>slf4j-api-N.jar</em>
+      will run perfectly fine with <em>slf4j-api-M.jar</em> for any N
+      and M. You only need to ensure that the version of your binding
+      matches that of the slf4j-api.jar. You do not have to worry
+      about the version of slf4j-api.jar used by a given dependendency
+      in your project. You can always use any version of
+      <em>slf4j-api.jar</em>, and as long as the version of
+      <em>slf4j-api.jar</em> and its binding match, you should be
+      fine.
+      </p>
+
+      <p>At initialization time, if SLF4J suspects that there may be a
+      api vs. binding version mismatch problem, it will emit a warning
+      about the suspected mismatch.
+      </p>
+
+
       <h3><a name="consolidate" href="#consolidate">Consolidate
       logging via SLF4J</a></h3>
 

-----------------------------------------------------------------------

Summary of changes:
 slf4j-site/src/site/pages/codes.html   |    2 +-
 slf4j-site/src/site/pages/css/site.css |   22 ++++++++++------
 slf4j-site/src/site/pages/manual.html  |   43 ++++++++++++++++++++++++++++++++
 3 files changed, 58 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
SLF4J: Simple Logging Facade for Java


More information about the slf4j-dev mailing list