Lines Matching +full:install +full:- +full:classic
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
6 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
14 <script type="text/javascript" src="js/jquery-min.js"></script>
27 java.util.logging, logback and log4j. SLF4J allows the end-user to
29 Note that SLF4J-enabling your library/application implies the
31 <em>slf4j-api-${project.version}.jar</em>.</p>
34 class path, then SLF4J will default to a no-operation
48 no-ifs-or-buts compatible with SLF4J version 1.6.x.
85 <em>slf4j-api-${project.version}.jar</em> to your class path.</p>
91 SLF4J: Defaulting to no-operation (NOP) logger implementation
99 <em>slf4j-simple-${project.version}.jar</em> so that your class
103 <li>slf4j-api-${project.version}.jar</li>
104 <li>slf4j-simple-${project.version}.jar</li>
110 <pre class="output">0 [main] INFO HelloWorld - Hello World</pre>
116 for SLF4J. Note the use of {}-placeholders on line 15. See the
157 <dt><em>slf4j-log4j12-${project.version}.jar</em>
164 <dt><em>slf4j-jdk14-${project.version}.jar</em> </dt>
168 <dt><em>slf4j-nop-${project.version}.jar</em></dt>
173 <dt><em>slf4j-simple-${project.version}.jar</em></dt>
181 <dt><em>slf4j-jcl-${project.version}.jar</em></dt>
189 …<dt><em>logback-classic-${logback.version}.jar (requires logback-core-${logback.version}.jar)</em>…
195 <a href="http://logback.qos.ch/apidocs/ch/qos/logback/classic/Logger.html">
196 <code>ch.qos.logback.classic.Logger</code></a> class is a
212 to log4j, just replace slf4j-jdk14-${project.version}.jar with
213 slf4j-log4j12-${project.version}.jar.
219 example, the slf4j-log4j12-${project.version}.jar binding is
221 to <em>slf4j-api-${project.version}.jar</em>, you simply drop
228 <p><a href="images/concrete-bindings.png">
229 <img border="1" src="images/concrete-bindings.png" alt="click to enlarge" width="800"/>
249 <p>Authors of widely-distributed components and libraries may
251 logging framework on their end-user. Thus, the end-user may
260 the class path, then slf4j-api will default to a no-operation
267 some biology-related framework depending on SLF4J for
269 end-user, Wombat's distribution includes <em>slf4j-api.jar</em>
272 out-of-the-box, and without requiring the end-user to download a
273 binding from SLF4J's web-site. Only when the end-user decides to
274 enable logging will she need to install the SLF4J binding
280 on any SLF4J binding but only depend on slf4j-api</b>. When a
282 that binding is imposed on the end-user negating the purpose of
283 SLF4J. Note that declaring a non-transitive dependency on a
285 end-user.</p>
302 <p><span class="label notice">logback-classic</span> If you wish
303 to use logback-classic as the underlying logging framework, all
304 you need to do is to declare "ch.qos.logback:logback-classic" as
306 addition to <em>logback-classic-${logback.version}.jar</em>,
307 this will pull <em>slf4j-api-${project.version}.jar</em> as well
308 as <em>logback-core-${logback.version}.jar</em> into your
310 <em>logback-core-${logback.version}</em> or
311 <em>slf4j-api-${project.version}.jar</em> is not wrong and may
319 <artifactId>logback-classic</artifactId>
327 to declare "org.slf4j:slf4j-log4j12" as a dependency in your
329 <em>slf4j-log4j12-${project.version}.jar</em>, this will pull
330 <em>slf4j-api-${project.version}.jar</em> as well as
331 <em>log4j-${log4j.version}.jar</em> into your project. Note
333 <em>log4j-${log4j.version}.jar</em> or
334 <em>slf4j-api-${project.version}.jar</em> is not wrong and may
341 <artifactId>slf4j-log4j12</artifactId>
350 "org.slf4j:slf4j-jdk14" as a dependency in your <em>pom.xml</em>
352 <em>slf4j-jdk14-${project.version}.jar</em>, this will pull
353 <em>slf4j-api-${project.version}.jar</em> into your project.
355 <em>slf4j-api-${project.version}.jar</em> is not wrong and may
362 <artifactId>slf4j-jdk14</artifactId>
372 <em>slf4j-jdk14.jar</em> or <em>slf4j-log4j12.jar</em> used to
378 of slf4j-api are compatible. Client code compiled with
379 slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for
381 binding matches that of the slf4j-api.jar. You do not have to
382 worry about the version of slf4j-api.jar used by a given
386 <p>Mixing different versions of <em>slf4j-api.jar</em> and SLF4J
388 slf4j-api-${project.version}.jar, then you should also use
389 slf4j-simple-${project.version}.jar, using
390 slf4j-simple-1.5.5.jar will not work.</p>
394 slf4j-api are compatible. Client code compiled with
395 <em>slf4j-api-N.jar</em> will run perfectly fine with
396 <em>slf4j-api-M.jar</em> for any N and M. You only need to
398 slf4j-api.jar. You do not have to worry about the version of
399 slf4j-api.jar used by a given dependency in your project. You
400 can always use any version of <em>slf4j-api.jar</em>, and as
401 long as the version of <em>slf4j-api.jar</em> and its binding
406 an slf4j-api vs. binding version mismatch problem, it will emit
419 this common use-case by providing bridging modules for JCL,
429 key-value pairs which can then be inserted by the logging
475 <td>Fail-fast operation</td>
481 no-operation implementation.
502 <em>jcl-over-slf4j.jar</em>, will allow your project to
505 log4j-over-slf4j.jar and jul-to-slf4j modules will allow
516 <td>The <a href="migrator.html">slf4j-migrator</a> utility