-
-
Notifications
You must be signed in to change notification settings - Fork 975
/
news.html
executable file
·1824 lines (1379 loc) · 66.1 KB
/
news.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<title>SLF4J News</title>
<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" />
<link rel="stylesheet" type="text/css" href="css/prettify.css" />
</head>
<body onload="prettyPrint()">
<script type="text/javascript">prefix='';</script>
<script type="text/javascript" src="js/prettify.js"></script>
<script src="templates/header.js" type="text/javascript"></script>
<div id="left">
<script src="templates/left.js" type="text/javascript"></script>
</div>
<div id="right">
<script src="templates/right.js" type="text/javascript"></script>
</div>
<div id="content">
<h1>SLF4J News</h1>
<p>Please note that you can receive SLF4J related announcements by
subscribing to the <a
href="http://www.qos.ch/mailman/listinfo/announce">QOS.ch
announce</a> mailing list.
</p>
<hr noshade="noshade" size="1"/>
<h3>xxx April, 2016 - Release of SLF4J 1.7.21</h3>
<p><code>LoggerFactory</code> makes sure to release all resources
referenced by SubstituteLoggerFactory post-initialization. See also
<a href="http://jira.qos.ch/browse/SLF4J-366">SLF4J-366</a>
</p>
<hr noshade="noshade" size="1"/>
<h3>March 29th, 2016 - Release of SLF4J 1.7.20</h3>
<p>Fixed initialization problem encountered on the Google App
Engine platform with SLF4J version 1.7.19 but not other versions.
The problem was reported in <a
href="http://jira.qos.ch/browse/SLF4J-363">SLF4J-363</a> by Osvaldo
Pinali Doederlein.
</p>
<hr noshade="noshade" size="1"/>
<h3>March 14th, 2016 - Release of SLF4J 1.7.19</h3>
<p>Fixed <code>NullPointerException</code> thrown by
org.slf4j.helpers.SubstituteLogger.isDelegateEventAware(SubstituteLogger.java:353). This
issue was reported by Jeffrey Zhao in <a
href="http://jira.qos.ch/browse/SLF4J-361">SLF4J-361</a>.</p>
<p>Initialization of the slf4j-log4j12 module is now thread safe
fixing <a href="http://jira.qos.ch/browse/SLF4J-358">SLF4J-358</a>.
</p>
<p>Initialization of the slf4j-jdk14 module is now thread safe
fixing <a href="http://jira.qos.ch/browse/SLF4J-359">SLF4J-359</a>.
</p>
<hr noshade="noshade" size="1"/>
<h3>26th of February, 2016 - Release of SLF4J 1.7.18</h3>
<p>Initialization of the slf4j-simple module is now thread safe
fixing <a href="http://jira.qos.ch/browse/SLF4J-356">SLF4J-356</a>.
</p>
<p>Fixed Import-Package statement in MANIFEST.MF for the
slf4j-log4j12 module. This isssue was reported by Mathieu Sebire in
<a href="jira.qos.ch/browse/SLF4J-357">SLF4J-357</a> who also
provided the relevant pull request.
</p>
<hr noshade="noshade" size="1"/>
<h3>19th of February, 2016 - Release of SLF4J 1.7.17</h3>
<p>When running under Android, skip binding ambiguity check during
initialization for better performance. The fix introduced in version 1.7.14
was not effective.
</p>
<hr noshade="noshade" size="1"/>
<h3>11th of February, 2016 - Release of SLF4J 1.7.16</h3>
<p>The <code>MANIFEST.MF</code> file in slf4j-api.jar module was
missing an export statement for the <em>org.slf4j.event</em>
package. <code>MANIFEST.MF</code> files in other modules were
missing the mirroring import statements.
</p>
<hr noshade="noshade" size="1"/>
<h3>9th of February, 2016 - Release of SLF4J 1.7.15</h3>
<p>In previous versions of SLF4J, if the application was already
multi-threaded at the time the first SLF4J logger was created, logs
made during the SLF4J initialization phase were lost. New code
added in relation with <a
href="http://jira.qos.ch/browse/SLF4J-353">SLF4J-353</a> fixes this
problem by storing and replaying logging calls made during
initialization.
</p>
<hr noshade="noshade" size="1"/>
<h3>24th of January, 2016 - Release of SLF4J 1.7.14</h3>
<p>The assignment of the INITIALIZATION_STATE variable in
<code>LoggerFactory</code> is now guaranteed to be consistent for
multi-thread initializations. More specifically, only one thread
will see INITIALIZATION_STATE as UNINITIALIZED with all other
threads observing either ONGOING_INITIALIZATION or the final result
of the initialization. However, SLF4J initialization is still
non-blocking and re-entrant, in the sense that if some thread tries
to obtain loggers during ongoing initialization by another (or
same) thread, instances of <code>SubstituteLogger</code> are
returned. This fixes <a
href="http://jira.qos.ch/browse/SLF4J-167">SLF4J-167</a>.
</p>
<p>Moved delegation check loop from <em>log4j-over-slf4j.jar</em>
to <em>slf4j-log4j12.jar</em> for better targeted loop checks. The
rationale behind the change is explained by Frans Orsel in <a
href="http://jira.qos.ch/browse/SLF4J-345">SLF4J-345</a> who also
provided the relevant pull request.
</p>
<p>During initialization the binding ambiguity check is skipped
under Android in order to improve performance. This change was
requested by Nitin Verma in <a
href="http://jira.qos.ch/browse/SLF4J-328">SLF4J-328</a> who also
provided the relevant patch.
</p>
<p>The <code>StaticMarkerBinder</code> and
<code>StaticMDCBinder</code> classes shipping in various SLF4J
bindings now offer a <code>getSingletion()</code> method. The
<code>org.slf4j.MDC</code> and <code>MarkerFactory</code> classes
now perform binding by invoking the <code>getSingleton()</code>
method first and if in the presence of an older version of SLF4J
with said method missing, then by accessing the SINGLETON
field. This backward compatible change was requested by Rufus
Alexander in <a
href="http://jira.qos.ch/browse/SLF4J-347">SLF4J-347</a> in order
to implement an SLF4J binding in Clojure, namely <a
href="https://github.com/fzakaria/slf4j-timbre">slf4j-timbre</a>.
</p>
<p>Fix the OSGI <code>Bundle-Version</code> property in the
<em>MANIFEST.MF</em> of osgi-over-slf4j module. This issue was
reported by Antoine Dessaigne in <a
href="http://jira.qos.ch/browse/SLF4J-341">SLF4J-341</a>.
</p>
<hr noshade="noshade" size="1"/>
<h3>10th of November, 2015 - Release of SLF4J 1.7.13</h3>
<p>Fixed <code>LoggerFactory</code> initialisation problem in
presence of SecurityManager denying "createSecurityManager" runtime
permission. See <a
href="http://jira.qos.ch/browse/SLF4J-324">SLF4J-324</a> for
further details.
</p>
<p>Fixed issue with <code>BasicMDCAdapter</code> leaking MDC
information to non-child threads. This problem was reported by
Lukasz Cwik in <a
href="http://jira.qos.ch/browse/SLF4J-316">SLF4J-316</a> who also
provided the relavant pull request.
</p>
<p>More robust handling of ill-formatted input strings by
SLF4JBridgeHandler. This issue was reported in <a
href="http://jira.qos.ch/browse/SLF4J-337">SLF4J-337</a> by Rodolfo
Udo Labsch.
</p>
<p>House cleaning of our project's Maven <em>pom.xml</em> files, an
initiative undertaken by Jeremy Landis.
</p>
<p>Added <code>getAdditivity()</code> method method in
<code>Category</code> class in the log4j-over-slf4j module. This
addition was requested by Milo Felipe <a
href="http://jira.qos.ch/browse/SLF4J-309">SLF4J-309</a> with
Dimitrios Liapis providing the relavant pull request.
</p>
<p>Added the <code>assertLog(boolean, String)</code> method in the
<code>Category</code> class, in module log4j-over-slf4j.</p>
<p>In the log4j-over-slf4j module, removed misplaced Layout.java
file. This issue was reported in <a
href="http://jira.qos.ch/browse/SLF4J-218">SLF4J-218</a> by Joshua
M Steward with Alfredo Ramos providing the relavant pull request.
</p>
<hr noshade="noshade" size="1"/>
<h3>March 26th, 2015 - Release of SLF4J 1.7.12</h3>
<p>All java files have been reformatted to with the code formatter
style defined in <i>codeStyle.xml</i>. This style uses 4 spaces for
indentation and a maximum line width of 160.</p>
<p>As SLF4J requires JDK 1.5 or later, the
<code>Bundle-RequiredExecutionEnvironment</code> declaration in the
various MANIFEST files have been updated to J2SE-1.5.
</p>
<p>Added missing Bundle-ManifestVersion attribute in the MANIFEST
files in log4j-over-slf4j. The issue was raised in <a
href="http://jira.qos.ch/browse/SLF4J-321">SLF4J-231</a> by Nikolas
Falco who also provided the the appropriate pull request. </p>
<p>Added <code>getAppender(String)</code> method in
<code>Category</code> class in the log4j-over-slf4j module. This
addition was requested by Ramon Gordillo in <a
href="http://jira.qos.ch/browse/SLF4J-319">SLF4J-319</a>.
</p>
<p>Added <code>setThreshold</code> method in
<code>AppenderSkeleton</code> class in the log4j-over-slf4j
module. This addition was requested by Dimitrios Liapis who also
provided the appropriate pull request.
</p>
<p>Added <code>getParent</code> method in <code>Category</code>
class in the log4j-over-slf4j module. This addition was requested
by Himanshu Bhardwaj in <a
href="http://jira.qos.ch/browse/SLF4J-318">SLF4J-318</a>.
</p>
<hr noshade="noshade" size="1"/>
<h3>6th of January, 2015 - Release of SLF4J 1.7.10</h3>
<p>The <code>MDC.putCloseable</code> method now explicitly returns
<code>MDC.MDCloseable</code> instead of the more generic
<code>java.io.Closeable</code>. This in turn allows one to write
try-with-resources statement without a catch clause. Many thanks to
William Delanoue for proposing this change.</p>
<p>The various constructors in <code>FileAppender</code> in the
log4j-over-slf4j module are now public.
</p>
<hr noshade="noshade" size="1"/>
<h3>16th of December, 2014 - Release of SLF4J 1.7.9</h3>
<p class="highlight"><a href="codes.html#loggerNameMismatch">Spot
incorrectly named loggers</a> by setting the
<code>slf4j.detectLoggerNameMismatch</code> system property to
true.</p>
<p><a href="codes.html#loggerNameMismatch">Spot incorrectly named
loggers</a> by setting the
<code>slf4j.detectLoggerNameMismatch</code> system property to
true. This significant feature was contributed by Alexander
Dorokhine.</p>
<p>Added <code>MDC.putCloseable</code> method so that it can be
used as a <a
href="https://docs.oracle.com/javase/7/docs/technotes/guides/language/try-with-resources.html">closeable
resource</a> under Java 7.</p>
<p>Added <code>getContext</code> method returning a hashtable in
org.apache.log4j.MDC in the log4j-over-slf4j module.
</p>
<p>The introduction of the @Nonnull JSR 305 annotation in SLF4J
version 1.7.8 causes the Scala compiler to fail. This is issue has
been documented in <a
href="https://issues.scala-lang.org/browse/SI-5420">SI-5420</a>. Given
that many Scala users will be affected by this issue for the
foreseeable future, we have decided to renounce the user of JSR 305
annotations in SLF4J for the time being.
</p>
<p>Numerous small code improvements too minor to be listed
here.</p>
<hr noshade="noshade" size="1"/>
<h3>4th of April, 2014 - Release of SLF4J 1.7.7 </h3>
<p>SFL4J API now uses generics. This enhancement was contributed by
Otavio Garcia. Due to erasure of generics in Java, the changes are
backward-compatible.</p>
<p>The slf4j-migrator can now convert statements using the long deprecated
<code>Category</code> class.</p>
<p>Added the <code>SimpleLayout</code> and
<code>FileAppender</code> classes to the log4j-over-slf4j
module.</p>
<h3>February 5th, 2014 - Release of SLF4J 1.7.6</h3>
<p>Added slf4j-android module to the slf4j distribution. This
module is contributed by Andrey Korzhevskiy.</p>
<p>Loggers created during the initialization phase are no longer
<code>NOPLoggers</code> which drop all logging calls. Instead,
SLF4J now creates substitute loggers which delegate to the
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>
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>.
</p>
<p>Concunrrency improvement in <code>MessageFormatter</code>. This
improvement was contributed by Vivek Pathak in a <a
href="https://github.com/qos-ch/slf4j/pull/52">pull
request</a>.</p>
<p>Concunrrency improvement in
<code>BasicMarkerFactory</code>. This improvement was contributed
by Mikhail Mazursky in a <a
href="https://github.com/qos-ch/slf4j/pull/40">pull
request</a>.</p>
<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>.
</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>
<p>In the log4j-over-slf4j module, added empty implementations for
<code>OptionHander</code>, <code>WriterAppender</code>,
<code>ConsoleAppender</code> and <code>AppenderSkeleton</code>
classes.
</p>
<hr noshade="noshade" size="1"/>
<h3>25th of March, 2013 - Release of SLF4J 1.7.5</h3>
<p class="highlight">Given the significance of these performance
improvements, users are highly encouraged to migrate to SLF4J
version 1.7.5 or later. </p>
<p><span class="label notice">performance improvements</span> The
logger factories in most SLF4J modules namely in jcl-over-slf4j,
log4j-over-slf4j, slf4j-jcl, slf4j-jdk14, slf4j-log4j12, and
slf4j-simple now use a <code>ConcurrentHashMap</code> instead of a
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>
by Taras Tielkes who also provided the relevant patch.
</p>
<hr noshade="noshade" size="1"/>
<h3>18th of March, 2013 - Release of SLF4J 1.7.4</h3>
<p>Added a package private <code>reset()</code> method to
<code>SimpleLoggerFactory</code> for testing purposes.</p>
<hr noshade="noshade" size="1"/>
<h3>15th of March, 2013 - Release of SLF4J 1.7.3</h3>
<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>
<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
Thomas Mortagne.</p>
<hr noshade="noshade" size="1"/>
<h3>11th of October, 2012 - Release of SLF4J 1.7.2</h3>
<p>Added osgi-over-slf4j module which serves as an OSGi LogService
implementation delegating to slf4j. This module is maintained by
Matt Bishop and Libor Jelinek.</p>
<p> Christian Trutz added missing PatternLayout class as well as
several methods in the <code>Logger</code> and
<code>Category</code> classes. See commit 442e90ba5785cba9 dated
September 27th 2012 for details.
</p>
<p>Added org.slf4j.simpleLoggerwarnLevelString in slf4j-simple
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>
<hr noshade="noshade" size="1"/>
<h3>14th of September, 2012 - Release of SLF4J 1.7.1</h3>
<p><a
href="apidocs/org/slf4j/impl/SimpleLogger.html"><code>SimpleLogger</code></a>
now supports writing to a file. The property names for configuring
<code>SimpleLogger</code> have been modified to be consistently in
camel case. More configuration options have been added. In the
absence of configuration directives, <code>SimpleLogger</code> will
behave exactly the same as in the past. <b>If you are one of the
few users configuring <code>SimpleLogger</code> with configuration
properties, you will need to adapt to the new and more consistent
property names.</b></p>
<hr noshade="noshade" size="1"/>
<h3>6th of September, 2012 - Release of SLF4J 1.7.0</h3>
<p><span class="bold big green">SLF4J now requires JDK 1.5.</span></p>
<p>Printing methods in the <a
href="apidocs/org/slf4j/Logger.html">Logger</a> interface now offers
variants accepting <a
href="http://docs.oracle.com/javase/1.5.0/docs/guide/language/varargs.html">varargs</a>
instead of Object[]. Given that under the hood, the Java compiler
transforms varargs into an array, this change is totally 100%
no-ifs-or-buts backward compatible with all existing client
code. </p>
<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
Andersen.</p>
<hr noshade="noshade" size="1"/>
<h3>11th of June, 2012 - Release of SLF4J 1.6.6</h3>
<p>Source repository has been moved to <a
href="https://github.com/qos-ch/slf4j">https://github.com/qos-ch/slf4j</a>
on github.</p>
<p>In case multiple bindings are found on the class path, SLF4J
will now output the name of the framework/implementation class it
binds with.</p>
<p><a
href="apidocs/org/slf4j/impl/SimpleLogger.html">SimpleLogger</a>
now supports configuration properties. </p>
<p>LoggerWrapper in the slf4j-ext module now correctly deals with
markers. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=265">bug #265</a>
reported by Dario Campagna.</p>
<p>The log4j-over-slf4j module now supports legacy projects
providing their own log4j <code>LoggerFactory</code>. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=234">bug #234</a>
reported by Laurent Pellegrino with Piotr Jagielski providing the
appropriate patch.</p>
<h3>4th of June, 2012 - Release of SLF4J 1.6.5</h3>
<p>In the slf4j-log4j12 module, upgraded the log4j dependency to
version 1.2.17.</p>
<p>Added removeHandlersForRootLogger() method to <code><a
href="apidocs/org/slf4j/bridge/SLF4JBridgeHandler.html">SLF4JBridgeHandler</a></code>
class.</p>
<p>The log4j-over-slf4j module now exports all its packages in its
manifest. This issue was reported in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=262">262</a> by
Mikhail Mazursky who also provided the relevant patch.
</p>
<h3>October 31st, 2011 - Release of SLF4J 1.6.4</h3>
<p>Fixed in thread-safety issues in <code>BasicMDCAdapter</code>
fixing <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=203">bug
#203</a> and <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=224">bug
#224</a>. Note that <code>BasicMDCAdapter</code> is only used with
the slf4j-jdk14.jar binding.
</p>
<p><code>BasicMDCAdapter</code> invoked a method introduced in JDK
1.5 preventing it from running under JDK 1.4. Interestingly enough,
this issue has never been reported by the user community.</p>
<h3>October 17th, 2011 - Release of SLF4J 1.6.3</h3>
<p><code>LogEvent</code> class in slf4j-ext module now correctly
passes the event data as a parameter object. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=246">bug #246</a>
reported by Ralph Goers.
</p>
<p>Added missing OSGi manifest to the jul-to-slf4j module. This
fixes <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=166">bug
#166</a> reported by Ekkehard Gentz. </p>
<p>In the log4j-over-slf4j module, added missing
<code>getAllAppenders</code>() method in <code>Category</code>
class. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=235">bug #235</a>
reported by Anthony Whitford.
</p>
<h3>August 19th, 2011 - Release of SLF4J 1.6.2</h3>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=138">bug
#138</a>. SLF4J will no longer complain about multiple SLF4J
bindings when running under a Weblogic server.
</p>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=228">bug
#228</a>. When running under IBM's JDK, and if no binding can be
found, SLF4J will no longer throw a
<code>NoClassDefFoundError</code>. Instead, it will default to an
NOP implementation. Under the same circumstances but with Sun's
JDK, SLF4J already defaulted to an NOP implementation since release
1.6.0.</p>
<p>Added certain missing classes to the log4j-over-slf4j module as
requested in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=225">bug 225</a> by
Josh Stewart.
</p>
<hr noshade="noshade" size="1"/>
<h3>July 5th, 2010 - Release of SLF4J 1.6.1</h3>
<p>Updated log4j dependency to version 1.2.16 and <a
href="http://cal10n.qos.ch/">CAL10N</a> dependency to version
0.7.4.
</p>
<p>Fixed missing versioning OSGi metadata in the log4j-over-slf4j
module. This problem was reported in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=187">bug 187</a> by
David Savage.
</p>
<hr noshade="noshade" size="1"/>
<h3>May 8th, 2010 - Release of SLF4J 1.6.0</h3>
<p>It is expected that <em>all</em> SLF4J releases in the 1.6.x
series will be mutually compatible.
</p>
<p>As of SLF4J version 1.6.0, in the absence of an SLF4J binding,
slf4j-api will default to a no-operation implementation discarding
all log requests. Thus, instead of throwing an exception, SLF4J
will emit a single warning message about the absence of a binding
and proceed to discard all log requests without further
protest. See also the <a href="manual.html#libraries">relevant
section</a> in the user manual.
</p>
<p>In the presence of multiple parameters and if the last argument
in a logging statement is an exception, then SLF4J will now presume
that the user wants the last argument to be treated as an exception
and not a simple parameter. See the relevant <a
href="faq.html#paramException">FAQ entry</a> for further
details. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=70">bug 70</a>
submitted by Joern Huxhorn who also provided the relevant patch.
</p>
<p>The <code>log</code> method in <code>LocationAwareLogger</code>
interface now admits an additional parameter of type
<code>Object[]</code> representing additional arguments of the log
request. Due to this modification, slf4j-api version 1.6.x will not
work with bindings shipping with SLF4J 1.5.x -- bindings shipping
with 1.6.x must be used.
</p>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=150">bug 150</a> by
implementing missing <code>resetConfiguration()</code> and
<code>shutdown()</code> methods in <code>LogManager</code> (in
log4j-over-slf4j) as nop. In addition, the
<code>getCurrentLoggers()</code> method has been implemented by
returning an empty enumeration.
</p>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=170">bug 170</a> by
a bare-bones implementation of the <code>NDC</code> class in
log4j-over-slf4j.</p>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=175">bug 175</a> by
synchronizing access to the loggerNameList field.</p>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=164">bug 164</a>
observed when SLF4J artifacts were placed under
java.endorsed.dirs.</p>
<p>Fixed sub-optimal list type usage in
<code>SLF4JLogFactory</code> as reported in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=179">bug 179</a> by
Sebastian Davids.
</p>
<p>Fixed documentation inconsistency in <code>SLF4JLog</code> as
reported in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=180">bug 180</a> by
Sebastian Davids.
</p>
<hr noshade="noshade" size="1"/>
<h3>February 25th, 2010 - Release of SLF4J 1.5.11</h3>
<p>Users yet unfamiliar with SLF4J sometimes unknowingly place both
<em>log4j-over-slf4j.jar</em> and <em>slf4j-log4j12.jar</em>
simultaneously on the class path causing stack overflow
errors. Simultaneously placing both <em>jcl-over-slf4j.jar</em> and
<em>slf4j-jcl.jar</em> on the class path, is another occurrence of
the same general problem. As of this version, SLF4J preempts the
inevitable stack overflow error by throwing an exception with
details about the actual cause of the problem. This is deemed to be
better than leaving the user wondering about the reasons of the
<code>StackOverflowError</code>.
</p>
<p>Fixed <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=168">bug
168</a>. In case log4j-over-slf4j is used and a logback appender
requires a third party library which depends on log4j, the
<code>log(String FQCN, Priority p, Object msg, Throwable t)</code>
method in log4j-over-slf4j's Category class would throw an
<code>UnsupportedOperationException</code>. Problem reported by Seth
Call.</p>
<hr noshade="noshade" size="1"/>
<h3>December 3rd, 2009 - Release of SLF4J 1.5.10</h3>
<p>SLF4J version 1.5.10 consist of bug fixes and minor
enhancements. It is totally backward compatible with SLF4J version
1.5.8. However, the slf4j-ext module ships with a new package called
<code>org.slf4j.cal10n</code> which adds <a
href="localization.html">localized/internationalized logging</a>
support as a thin layer built upon the <a
href="http://cal10n.qos.ch">CAL10N API</a>.</p>
<p><a href="http://www.slf4j.org/android/">SLF4J-android</a>,
maintained by <a
href="http://dbis.cs.unibas.ch/team/thorsten-moller/dbis_staff_view">Thorsten
Möller</a>, was added as a daughter project of SLF4J.
</p>
<p>Added missing "Export-Package" declaration for cal10n in the OSGi
manifest file for sfl4j-ext. This was requested in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=156">bug 156</a> by
Pete Muir.</p>
<p>In log4j-over-slf4j, added missing log(...) methods as requested
by Zoltan Szel in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=139">bug report
139</a>.</p>
<p>In log4j-over-slf4j, added missing <code>LogManager</code> class
as requested by Rick Beton in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=150">bug report
150</a>.</p>
<p>In the slf4j-ext module, added
<code>getCopyOfChildTimeInstruments</code> and
<code>getCopyOfGlobalStopWatch</code> methods to the
<code>Profiler</code> class. This enables developers to build their
own output formatters for a given Profiler. This feature was
requested by David Lindelöf in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=141">bug 141</a>.
</p>
<p>Fixed a <code>NullPointerException</code> occurring in unspecified
conditions as described in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=146">bug report
146</a> by Dapeng Ni.</p>
<p>Added missing OSGi manifest to the <em>log4j-over-slf4j</em>
module as requested by Wade Poziombka in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=117">bug 117</a>.
</p>
<p>OSGi manifests produced by SLF4J now replace the '-' character by
'.' in compliance with the OSGi specification. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=152">bug 152</a>
according to the patch supplied by Hugues Malphettes.
</p>
<p>Fixed packaging issue in jcl104-over-slf4j which inadvertently
produced a jar file as described in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=151">bug 151</a> by
Jesse McConnell.</p>
<hr noshade="noshade" size="1"/>
<h3>June 11th, 2009 - Release of SLF4J 1.5.8</h3>
<p>SLF4J version 1.5.8 consist of bug fixes. It is totally backward
compatible with SLF4J version 1.5.7.</p>
<p>The Maven pom file for the <code>log4j-over-slf4j</code> module
contained a compile time dependency on the <code>slf4j-jdk14</code>
module. The dependency should have been declared in the test
scope. This problem was reported by Jean-Luc Geering on the slf4j
user list.
</p>
<h3>June 10th, 2009 - Release of SLF4J 1.5.7</h3>
<p>SLF4J version 1.5.7 consist of bug fixes and minor
enhancements. It is totally backward compatible with SLF4J version
1.5.6.</p>
<p>In SLF4J versions 1.5.5 and 1.5.6, the <code>LoggerFactory</code>
class which is at the core of SLF4J, if a version compatibility
issue was detected, accidentally invoked a method which was
introduced in JDK 1.5. Thus, instead of issuing a clear warning
message, SLF4J would throw a
<code>NoClassDefFoundError</code>. Consequently, SLF4J would not run
with JDK 1.4 and earlier but only if a version incompatibility issue
was present. For example, if you were mixing
<em>slf4j-api-1.5.6.jar</em> with <em>slf4j-simple-1.4.2.jar</em>,
which are mutually incompatible. Please note that this bug affects
only SLF4J versions 1.5.5 and 1.5.6 <em>and</em> only in the
presence of incompatible versions of slf4j-api and its binding.
</p>
<p>SLF4J will now emit a warning if more than one binding is present
on the class path. This enhancement was proposed in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=132">bug 132</a>
contributed by by Robert Elliot.
</p>
<p>The Log interface implementations in the jcl-over-slf4j module
will now correctly cope with serialization. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=79">bug 79</a>
reported by Mathias Bogaert. Many thanks to Eric Vargo for precisely
identifying the problem and supplying the corresponding patch.</p>
<p>The log4j-over-slf4j module will now correctly
interact with logging frameworks supporting location information
such as java.util.logging and logback. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=131">bug 131</a>
reported by Marc Zampetti.
</p>
<p><code>SLF4JBridgeHandler</code> will no longer ignore log records
with an empty message. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=108">bug 108</a>
reported by Pepijn Van Eeckhoudt and independently by Dan Lewis.
</p>
<p>In case the <code>toString()</code> method of a parameter throws
an exception, <code>MessageFormatter</code> will now print an error
message, instead of letting the exception bubble higher up as
previously. This fixes <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=112">bug 112</a>
submitted by Joern Huxhorn.
</p>
<hr noshade="noshade" size="1"/>
<h3>November 21st, 2008 - Release of SLF4J 1.5.6</h3>
<p>SLF4J version 1.5.6 consists of bug fixes. Users are encouraged
to upgrade to SLF4J version 1.5.6. The upgrade should pose no
problems. Nevertheless, you might still want to refer to the SLF4J
<a href="compatibility.html">compatibility report</a>.
</p>
<p>Fixed long standing <a
href="http://jira.qos.ch/browse/LBCLASSIC-87">LBCLASSIC-87</a> and
its younger sibling <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=113">bug
113</a>. With each call to getLogger() method,
<code>LoggerContext</code> will now retrieve the ILoggerFactory
afresh from <code>StaticLoggerBinder</code>. This change enables
context selectors of native implementations, e.g logback, to work
correctly.
</p>
<p>Fixed <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=114">bug
114</a> reported by Jason Arndt. Corrected the way
<code>XLogger</code> (in slf4j-ext) passes its fully qualified class
name so that the underlying logging system can correctly compute
location information.
</p>
<p>The <code>install()</code> method of
<code>SLF4JBridgeHandler</code> will no longer reset the entire
j.u.l. environment but solely add a <code>SLF4JBridgeHandler</code>
instance to jul's root logger. By the same token, the
<code>uninstall()</code> method will remove previously added
<code>SLF4JBridgeHandler</code> instances without making any other
modifications to the j.u.l. configuration.
</p>
<p>Added <code>MDCStrLookup</code> to slf4j-ext. This class can be
used with Apache Commons Lang's <code>StrSubstitutor</code> class to
inject values in the SLF4J MDC into strings. Information on
StrSubstitutor can be found at <a
href="http://commons.apache.org/lang/api-release/org/apache/commons/lang/text/StrSubstitutor.html">StrSubstitutor
javadoc</a>.
</p>
<hr noshade="noshade" size="1"/>
<h3>October 17th, 2008 - Release of SLF4J 1.5.5</h3>
<p>The version check mechanism introduced in SLF4J 1.5.4 was
inconsistent with the large size of SLF4J's installed user base. We
cannot expect external SLF4J implementations to align their release
schedule with that of SLF4J. Consequently, this SLF4J version,
namely 1.5.5, retains versions checks but as an elective
process. For further details see the <a
href="faq.html#version_checks">relevant entry</a> in the FAQ.
</p>
<p>You are highly encouraged to upgrade to SLF4J version 1.5.5. The
upgrade should pose no problems. Nevertheless, you might still want
to refer to the SLF4J <a href="compatibility.html">compatibility
report</a>.
</p>
<h3>October 16th, 2008 - Release of SLF4J 1.5.4</h3>
<p>This version corrects critical bugs.
</p>
<p>Fixed <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=106">critical bug
106</a>. In previous versions of SLF4J, if during the initial
binding phase, the underlying logging system's default configuration
created or invoked loggers, a <code>NullPointerException</code>
would be thrown. Refer to the <a
href="codes.html#substituteLogger">in error codes</a> document for a
fuller explanation.</p>
<p>At initialization time, LoggerFactory will now check that the
version of the slf4j-binding matches that of slf4j-api. If there is
a mismatch a warning will be issued on the console. This should help
users identify SLF4J related problems more quickly.</p>
<p>Improvements in documentation as well as fix for <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=102">packaging
problems</a> related to <em>slf4j-ext</em> module.
</p>
<p>SLF4JBridgeHandler (part of jul-to-slf4j) now accounts for
loggers with resourceBundle as well parameters. This feature
requested by Darryl Smith in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=98">bug 98</a> and
by Jarek Gawor in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=103">bug
103</a>.</p>
<p>We now say that markers contain <em>references</em> to other
markers. We no longer talk about child markers. The javadocs of the
<code>Marker</code> interface have been updated to reflect this
change. Moreover, the <code>hasChildren()</code> method in the
Marker interface has been deprecated and a new method called
<code>hasReferences()</code> was added.
</p>
<hr noshade="noshade" size="1"/>
<h3>September 12th, 2008 - Release of SLF4J 1.5.3</h3>
<p>See also the <a href="compatibility.html#1_5_3">compatibility
report for this version</a>.
</p>
<p>Added a new module called slf4j-ext for slf4j-extensions. See <a
href="extensions.html">its documentation</a> for further
details.</p>
<p>Fixed <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=71">bug
71</a> which was re-opened by Manfred Geiler. SLF4J loggers now
survive serialization. By survive serialization, we mean
that the deserialized logger instance are fully functional. </p>
<p>The fix for <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=68">bug 68</a> as
implemented in version 1.5.1 was incomplete. Michael Furman supplied
a more complete fix which was incorporated in this release.</p>
<p>When slf4j bridges, e.g. jcl-over-slf4j or log4j-over-slf4j, were
used in conjunction with JUL as the underlying logging system,
JDK14LoggerAdapter created a LogRecord even for disabled log
statements. This performance issue was reported in <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=90">bug 90</a> by
Matthew Mastracci.
</p>
<p>Added support for array values, including multi-dimensional
arrays, as parameters. For example,</p>
<p class="source">log.debug("{} {}", "A", new int[] {1, 2}});</p>
<p>will print as "A [1, 2]" instead of "A [I@6ca1c" as
previously. This enhancement was proposed by "lizongbo".
</p>
<p>Parameter substitution code has been simplified. SLF4J now only
cares about the "{}" formatting anchor, that is the '{' character
immediately followed by '}'. Previously, the '{' had meaning on its
own. As a result of this change, users no longer need to escape the
'{' unless it is immediately followed by '}'. Existing messages
which escaped standalone '{' character will be printed with a
preceding backslash. However, no data loss in the printed messages
will occur.
</p>
<p>Added missing <code>getInstance</code> methods to the
<code>Category</code> class in the log4j-over-slf4j module, fixing
<a href="http://bugzilla.slf4j.org/show_bug.cgi?id=95">bug 95</a>
reported by Michael Rumpf.</p>
<hr noshade="noshade" size="1"/>
<h3>June 8th, 2008 - Release of SLF4J 1.5.2</h3>
<p>Improvements to SLF4J documentation as well as fix of <a
href="http://bugzilla.slf4j.org/show_bug.cgi?id=88">packaging
problems</a> related to <em>jul-to-slf4j.jar</em> and
<em>jcl104-over-slf4j.jar</em>.
</p>
<h3>June 5th, 2008 - Release of SLF4J 1.5.1</h3>
<p>See also the <a href="compatibility.html#1_5_1">compatibility
report for this version</a>.</p>
<p>In order to support JCL version 1.1.1, the
<em>jcl<b>104</b>-over-slf4j</em> module was renamed as
<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
reported by Niklas Gustavsson.
</p>