Lines Matching full:over
53 <h2 class="doAnchor" name="jcl-over-slf4j">Gradual migration to
56 <h4 class="doAnchor" name="jclOverSLF4J"><em>jcl-over-slf4j.jar</em></h4>
59 include the jar file <em>jcl-over-slf4j.jar</em>. This jar file is
62 the name "JCL over SLF4J."
65 <p>Our JCL over SLF4J implementation will allow you to migrate to
71 <em>jcl-over-slf4j.jar</em>. Subsequently, the selection of the
77 <em>jcl-over-slf4j.jar</em> will immediately and permanently solve
96 name="jclRecursion"><em>jcl-over-slf4j.jar</em> should not be
100 <p>JCL-over-SLF4J, i.e. <em>jcl-over-slf4j.jar</em>, comes in handy
117 <p>Please note that <em>jcl-over-slf4j.jar</em> and
126 <h2 class="doAnchor" name="log4j-over-slf4j">log4j-over-slf4j</h2>
128 <p>SLF4J ship with a module called <em>log4j-over-slf4j</em>. It
131 <em>log4j.jar</em> file with <em>log4j-over-slf4j.jar</em>, as
137 <p>The log4j-over-slf4j module contains replacements of most widely
147 <p>To use log4j-over-slf4j in your own application, the first step
149 <em>log4j-over-slf4j.jar</em>. Note that you still need an SLF4J
150 binding and its dependencies for log4j-over-slf4j to work properly.
167 <p>The <em>log4j-over-slf4j</em> module will not work when the
171 log4j-over-slf4j would be an insufficient replacement for
174 log4j-over-slf4j module should just work fine.
182 <p>There overhead of using log4j-over-slf4j instead of log4j
183 directly is relatively small. Given that log4j-over-slf4j
192 log4j-over-slf4j instead of log4j directly.
195 <h4 class="doAnchor" name="log4jRecursion">log4j-over-slf4j.jar
201 log4j. The presence of <em>log4j-over-slf4j.jar</em> will in turn
220 to other bridging modules, namely jcl-over-slf4j and
221 log4j-over-slf4j, which reimplement JCL and respectively log4j,
