Author: ceki
Date: Tue Apr 21 22:30:30 2009
New Revision: 1324
Modified:
slf4j/trunk/slf4j-site/src/site/pages/manual.html
Log:
- removed the words "depressingly" and "highly".
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 Tue Apr 21 22:30:30 2009
@@ -248,13 +248,12 @@
<p>Often times, a given project will depend on various
components which rely on logging APIs other than SLF4J. It is
- depressingly common to find projects depending on JCL,
- java.util.logging, log4j and SLF4J at the same time. It then
- becomes highly 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>.
+ 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
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
