Hello Thorbjørn,
The previous text, if not 100%, was nevertheless quite neutral. There is no need
to mention authorship in the SLF4J manual.
r...@slf4j.org wrote:
Author: ravn
Date: Sun Apr 26 13:09:12 2009
New Revision: 1330
Modified:
slf4j/trunk/slf4j-site/src/site/pages/manual.html
Log:
revised logback reference to mention same author and working well together
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 Sun Apr 26 13:09:12 2009
@@ -152,16 +152,8 @@
<p>There are also SLF4J bindings external to the SLF4J project,
e.g. <a href="http://logback.qos.ch/";>logback</a> which
- implements SLF4J natively. Logback's
- <a
href="http://logback.qos.ch/apidocs/ch/qos/logback/classic/Logger.html";>
- <code>ch.qos.logback.classic.Logger</code></a> class is a direct
- implementation of SLF4J's
- <a href="http://www.slf4j.org/apidocs/org/slf4j/Logger.html";>
- <code>org.slf4j.Logger</code></a> interface. Thus, using SLF4J
- in conjunction with logback involves strictly zero memory and
- computational overhead.
- </p>
-
+ implements SLF4J natively. Logback is authored by the same
+ programmer as slf4j, and they work very well together.</p>
<p>To switch logging frameworks, just replace slf4j bindings on
your class path. For example, to switch from java.util.logging
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
