mirror of https://github.com/qos-ch/slf4j
correct bugzilla links
This commit is contained in:
parent
1ddc1f72d1
commit
7ef791c4ae
|
|
@ -370,14 +370,14 @@
|
|||
appropriate logger implementation after the initilization phase
|
||||
completes. Only calls made to these loggers during the
|
||||
initialization phase are dropped. This enhacement was proposed in
|
||||
<a href="http://bugzilla.slf4j.org/show_bug.cgi?id=311">bug 311</a>
|
||||
<a href="http://jira.qos.ch/browse/SLF4J-302">SLF4J-302</a>
|
||||
by Chetan Mehrotra.
|
||||
</p>
|
||||
|
||||
<p>Improvements to the <code>exit()</code> and
|
||||
<code>throwing()</code> methods in <code>XLogger</code>. This
|
||||
enhacement was requested in <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=197">bug 197</a>.
|
||||
href="http://jira.qos.ch/browse/SLF4J-188">SLF4J-188</a>.
|
||||
</p>
|
||||
|
||||
<p>Concunrrency improvement in <code>MessageFormatter</code>. This
|
||||
|
|
@ -394,14 +394,14 @@
|
|||
<p><code>JCLLoggerAdapter</code> was incorrectly invoking
|
||||
<code>isDebugEnabled</code> calls in its <code>trace()</code>
|
||||
methods. This issue was reported in <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=281">bug 281</a>.
|
||||
href="http://jira.qos.ch/browse/SLF4J-272">SLF4J-272</a>.
|
||||
|
||||
</p>
|
||||
|
||||
<p>In the log4j-over-slf4j module, the <code>setLevel</code>
|
||||
method in the <code>Category</code> class. This fixes <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=279">bug
|
||||
279</a>. Alfredo Ramos provied the relevant patch.
|
||||
<p>In the log4j-over-slf4j module, the <code>setLevel</code> method
|
||||
in the <code>Category</code> class. This fixes <a
|
||||
href="http://jira.qos.ch/browse/SLF4J-270">SLF4J-270</a>. Alfredo
|
||||
Ramos provied the relevant patch.
|
||||
</p>
|
||||
|
||||
<p>In the log4j-over-slf4j module, added empty implementations for
|
||||
|
|
@ -425,7 +425,7 @@
|
|||
regular <code>HashMap</code> to cache logger instances. This change
|
||||
significantly improves logger retrieval times at the cost of some
|
||||
memory overhead. This improvement was requested in <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=298">bug #298</a>
|
||||
href="http://jira.qos.ch/browse/SLF4J-289">SLF4J-289</a>
|
||||
by Taras Tielkes who also provided the relevant patch.
|
||||
</p>
|
||||
|
||||
|
|
@ -444,13 +444,13 @@
|
|||
<p>The jul-to-slf4j bridge now correctly handles cases where the
|
||||
message string contains {}-placeholders but has no or zero
|
||||
parameters. This fixes <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=212">bug
|
||||
#212</a>. The relevant patch was provided by Matthew Preston in a
|
||||
git pull request.</p>
|
||||
href="http://jira.qos.ch/browse/SLF4J-203">SLF4J-203</a>. The
|
||||
relevant patch was provided by Matthew Preston in a git pull
|
||||
request.</p>
|
||||
|
||||
<p>Added missing methods and classes in log4j-over-slf4j module for
|
||||
Velocity compatibility. This issue was reported in <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=280">bug 280</a> by
|
||||
href="http://jira.qos.ch/browse/SLF4J-271">SLF4J-271</a> by
|
||||
Thomas Mortagne.</p>
|
||||
|
||||
<hr noshade="noshade" size="1"/>
|
||||
|
|
@ -471,10 +471,10 @@
|
|||
module.</p>
|
||||
|
||||
<p>Fixed <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=272">bug
|
||||
272</a>. All <code>Logger</code> implementations shipping with
|
||||
SLF4J use <code>Object...</code> instead of <code>Object[]</code>
|
||||
to avoid compiler warnings.</p>
|
||||
href="http://jira.qos.ch/browse/SLF4J-263">SLF4J-263</a>. All
|
||||
<code>Logger</code> implementations shipping with SLF4J use
|
||||
<code>Object...</code> instead of <code>Object[]</code> to avoid
|
||||
compiler warnings.</p>
|
||||
|
||||
|
||||
|
||||
|
|
@ -510,8 +510,8 @@
|
|||
|
||||
<p>The logger field (of type <code>java.util.logging.Logger</code>)
|
||||
in <code>JDK14LoggerAdapter</code> is now marked as transient. This
|
||||
fixes <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=261">bug
|
||||
#261</a>, a serialization problem reported by Thorbjørn Ravn
|
||||
fixes <a href="http://jira.qos.ch/browse/SLF4J-252">SLF4J-252</a>,
|
||||
a serialization problem reported by Thorbjørn Ravn
|
||||
Andersen.</p>
|
||||
|
||||
<hr noshade="noshade" size="1"/>
|
||||
|
|
@ -1039,7 +1039,7 @@
|
|||
<em>jcl-over-slf4j</em>. SLF4J will no longer ship with
|
||||
<em>jcl104-over-slf4j.jar</em> but with <em>jcl-over-slf4j.jar</em>.
|
||||
The related work responds to enhancement request discussed in <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=85">bug 85</a> as
|
||||
href="http://jira.qos.ch/browse/SLF4J-76">issue 76</a> as
|
||||
reported by Niklas Gustavsson.
|
||||
</p>
|
||||
|
||||
|
|
@ -1642,11 +1642,11 @@
|
|||
<h3>August 28th, 2005 - Release of SLF4J 1.0-beta7 and NLOG4J 1.2.17</h3>
|
||||
|
||||
<p>Spurred by <a
|
||||
href="http://bugzilla.slf4j.org/show_bug.cgi?id=3">bug report
|
||||
#3</a>, SLF4J binding code has been refactored and
|
||||
simplified. Logging systems implementing SLF4J interfaces have to
|
||||
have less work in order to bind with SLF4J. Moreover, these changes
|
||||
have no incidence on the published interface of SLF4J.
|
||||
href="http://jira.qos.ch/browse/SLF4J-1">SLF4J-1</a>, SLF4J binding
|
||||
code has been refactored and simplified. Logging systems
|
||||
implementing SLF4J interfaces have to have less work in order to
|
||||
bind with SLF4J. Moreover, these changes have no incidence on the
|
||||
published interface of SLF4J.
|
||||
</p>
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue