[slf4j-dev] svn commit: r773 - slf4j/trunk/slf4j-site/src/site/resources
ceki at slf4j.org
ceki at slf4j.org
Thu Mar 1 17:32:14 CET 2007
Author: ceki
Date: Thu Mar 1 17:32:14 2007
New Revision: 773
Modified:
slf4j/trunk/slf4j-site/src/site/resources/faq.html
Log:
minor improvements
Modified: slf4j/trunk/slf4j-site/src/site/resources/faq.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/resources/faq.html (original)
+++ slf4j/trunk/slf4j-site/src/site/resources/faq.html Thu Mar 1 17:32:14 2007
@@ -306,7 +306,7 @@
</table>
</dd>
- <dt><a name="maven2">What about Maven 2 transitive
+ <dt><a name="maven2">What about Maven2 transitive
dependencies? </a>
</dt>
@@ -314,10 +314,10 @@
<p>As an author of a library built with Maven2, you might
want to test your application using a binding, say
slf4j-log4j12 or logback-classic, without forcing log4j or
- logback-classic as a dependency on your users. As of SLF4J
- version 1.3, this quite very easy to accomplish. But first,
- since your library's code depends on the SLF4J API you will
- need to declare slf4j-api as a compile-time (default scope)
+ logback-classic as a dependency upon your users. As of SLF4J
+ version 1.3, this quite easy to accomplish. But first, since
+ your library's code depends on the SLF4J API you will need to
+ declare slf4j-api as a compile-time (default scope)
dependency.
</p>
<p> </p>
@@ -330,7 +330,7 @@
<p> </p>
<p>Limiting the transitivity of the SLF4J binding used in your
- tests can be easily accomplished by declaring the scope of the
+ tests can be accomplished by declaring the scope of the
SLF4J-binding dependency as "test". Here is an example:</p>
<p> </p>
More information about the slf4j-dev
mailing list