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

[Gitbot]

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  bc2121efb6437fe4b2deef38be9a0588c94627ba (commit)
      from  3a461317916651390d83891d3d4b73d9e38dcb28 (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=bc2121efb6437fe4b2deef38be9a0588c94627ba
http://github.com/ceki/slf4j/commit/bc2121efb6437fe4b2deef38be9a0588c94627ba

commit bc2121efb6437fe4b2deef38be9a0588c94627ba
Author: Ceki Gulcu <ceki at qos.ch>
Date:   Sat Dec 3 00:08:21 2011 +0100

    editorial changes

diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html
index afec6fd..c17de0c 100644
--- a/slf4j-site/src/site/pages/faq.html
+++ b/slf4j-site/src/site/pages/faq.html
@@ -666,11 +666,15 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
       <p><b>alternative 1) explicit exlusion</b></p>
 
       <p>Many software projects using Maven declare commons-logging as
-      a dependency. Thus, if you wish to migrate to SLF4J or use
+      a dependency. Therefore, if you wish to migrate to SLF4J or use
       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.
+      commons-logging. <a
+      href="http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.htm">Dependency
+      exclusion</a> is described in the Maven documentation. Excluding
+      commons-logging explicitly for multiple dependencies distributed
+      on several <em>pom.xml</em> files can be a cumbersome and a
+      relatively error prone process.
       </p>
 
       <p><b>alternative 2) provided scope</b></p>
@@ -713,19 +717,23 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
 
       <p><b>alternative 3) empty artifacts</b></p>
       
-      <p>An alternative approach is to depend on an empty
+      <p>An alternative approach is to depend on an <b>empty</b>
       <em>commons-logging.jar</em> artifact. This clever <a
       href="http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html">approach
-      was imagined</a> imagined and initially supported by Erik van
+      first was imagined</a> imagined and initially supported by Erik van
       Oosten.
       </p>
 
       <p>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.
+      high-availability Maven repository, replicated on several hosts
+      located in different geographical regions.</p>
+
+      <p>The following decleration adds the version99 repository to
+      the set of remote repositories searched by Maven. This
+      repository contains empty artifacts for commons-logging and
+      log4j. By the way, if you use the version99 repository, please
+      drop us a line at <version99 AT qos.ch>.
       </p>
 
       <pre class="prettyprint source"><repositories>
@@ -736,30 +744,38 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
   </repository>
 </repositories></pre>
       
-    <p>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.
+    <p>Declaring version 99-empty of commons-logging in the
+    <code><dependencyManagement></code> section of your project
+    will direct all transtive dependencies for commons-logging to
+    import version 99-empty, thus nicely addressing the
+    commons-logging exclusion problem. The classes for commons-logging
+    will be provided by jcl-over-slf4j. The following lines declare
+    commons-logging version 99-empty (in the dependency management
+    section) and declare jcl-over-slf4j as a dependency.
     </p>
     
 <pre class="prettyprint source"><dependencyManagement>
-  <dependency>
-    <groupId>commons-logging</groupId>
-    <artifactId>commons-logging</artifactId>
-    <version><b>99-empty</b></version>
-  </dependency>
-  ... other declarations...
+  <dependencies>
+    <dependency>
+      <groupId>commons-logging</groupId>
+      <artifactId>commons-logging</artifactId>
+      <version><b>99-empty</b></version>
+    </dependency>
+    ... other declarations...
+  </dependencies>
 </dependencyManagement>
 
-<!-- let's not forget to declare a dependency on jcl-over-slf4j -->
+<!-- Do not forget to declare a dependency on jcl-over-slf4j in the        -->
+<!-- dependencies section. Note that the dependency on commons-logging     -->
+<!-- will be imported transitively. You don't have to declare it yourself. -->
 <dependencies>
   <dependency>
     <groupId>org.slf4j</groupId>
     <artifactId>jcl-over-slf4j</artifactId>
     <version>${project.version}</version>
   </dependency>
-<dependencies>
+  ... other dependency declarations
+</dependencies>
 </pre>
 
 

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

Summary of changes:
 slf4j-site/src/site/pages/faq.html |   60 ++++++++++++++++++++++-------------
 1 files changed, 38 insertions(+), 22 deletions(-)


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