Author: ceki
Date: Fri Apr 17 14:39:13 2009
New Revision: 1309
Modified:
slf4j/trunk/slf4j-site/src/site/pages/legacy.html
Log:
with NOT switch
Modified: slf4j/trunk/slf4j-site/src/site/pages/legacy.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/legacy.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/legacy.html Fri Apr 17 14:39:13 2009
@@ -22,11 +22,11 @@
<p>Often, some of the components you depend on rely on a logging
API other than SLF4J. You may also assume that these components
- will switch to SLF4J in the immediate future. To deal with such
- circumstances, SLF4J ships with several bridging modules which
- redirect calls made to log4j, JCL and java.util.logging APIs to
- behave as if they were made to the SLF4J API instead. The figure
- below illustrates the idea.
+ will not switch to SLF4J in the immediate future. To deal with
+ such circumstances, SLF4J ships with several bridging modules
+ which redirect calls made to log4j, JCL and java.util.logging APIs
+ to behave as if they were made to the SLF4J API instead. The
+ figure below illustrates the idea.
</p>
<p></p>
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
