SLF4J user manual
The Simple Logging Facade for Java (SLF4J) serves as a simple @@ -38,14 +37,6 @@
SLF4J user manual
the addition of only a single mandatory dependency, namely slf4j-api-${latest.stable.version}.jar. -Where are the Maven coordinates?
- -At this time if you are only interested in obtaining the - coordinates for using SLF4J API with a logging backend, you can jump to the relevant section.
- -Salient historical changes
-since 1.6.0 If no binding is found on the class path, then SLF4J will default to a no-operation implementation. @@ -303,13 +294,11 @@
Binding with a logging
slf4j-reload4j-${latest.stable.version}.jar
-
- since 1.7.33
- Binding/provider for reload4j
- framework. Reload4j is a drop-in replacement for log4j
- version 1.2.7. You also need to place reload4j.jar
- on your class path.
+ since 1.7.33 Binding/provider for
+ reload4j
+ framework. Reload4j is a drop-in replacement for log4j version
+ 1.2.7. You also need to place reload4j.jar on your
+ class path.
slf4j-jdk14-${latest.stable.version}.jar
@@ -337,14 +326,7 @@ Binding with a logging
JCL.
- since 1.7.33 - Binding/provider for reload4j - framework. Reload4j is a drop-in replacement for log4j - version 1.2.7. You also need to place reload4j.jar - on your class path.
+- or -
- logback-classic-${logback-javax.version}.jar for use with Javax EE, requires logback-core-${logback-javax.version}.jar - -
SLF4J API SLF4J API ships - within the "org.slf4j:slf4j-api" artifact. You can explicitly - declare a dependency to it in your pom.xml file as - shown below. Note that most logging implementations will - automatically pull-in slf4j-api as a dependency. However, it is - often a good idea to declare an explicit dependency to slf4j-api - in order to fix the correct version of slf4j-api your project by - virtue of of Maven's "nearest definition" dependency mediation +
logback-classic If you wish + to use logback-classic as the underlying logging framework, all + you need to do is to declare "ch.qos.logback:logback-classic" as + a dependency in your pom.xml file as shown below. In + addition to logback-classic-${logback.version}.jar, + this will pull in + slf4j-api-${latest.stable.version}.jar as well as + logback-core-${logback.version}.jar into your + project. Note that explicitly declaring a dependency on + logback-core-${logback.version} or + slf4j-api-${latest.stable.version}.jar is not wrong and + may be necessary to impose the correct version of said artifacts + by virtue of Maven's "nearest definition" dependency mediation rule.
- -<dependency>
- <groupId>org.slf4j</groupId>
- <artifactId>slf4j-api</artifactId>
- <version>${latest.stable.version}</version>
-</dependency>
-
-
- logback-classic 1.3.x (Javax - EE) If you wish to use logback-classic for Javax EE as the underlying logging - framework, all you need to do is to declare - "ch.qos.logback:logback-classic" as a dependency in your - pom.xml file as shown below. In addition to - logback-classic-${logback-javax.version}.jar, this will - pull in slf4j-api-${latest.stable.version}.jar as well - as logback-core-${logback-javax.version}.jar into your - project. Note that explicitly declaring a dependency on - logback-core-${logback-javax.version} or - slf4j-api-${latest.stable.version}.jar is not wrong and - may be necessary to impose the correct version of said artifacts - by virtue of Maven's "nearest definition" dependency mediation - rule. -
- -<dependency>
- <groupId>ch.qos.logback</groupId>
- <artifactId>logback-classic</artifactId>
- <version>${logback-javax.version}</version>
-</dependency>
-
-
-
-
-
- logback-classic - 1.4.x - (Jakarta EE) - - If you wish to use logback-classic for Jakarta EE as the underlying logging framework, - all you need to do is to declare - "ch.qos.logback:logback-classic" as a dependency in your - pom.xml file as shown below. In addition to - logback-classic-${logback-jakarta.version}.jar, this - will pull in slf4j-api-${latest.stable.version}.jar as - well as logback-core-${logback-jakarta.version}.jar - into your project. Note that explicitly declaring a - dependency on logback-core-${logback-jakarta.version} - or slf4j-api-${latest.stable.version}.jar is not wrong - and may be necessary to impose the correct version of said - artifacts by virtue of Maven's "nearest definition" dependency - mediation rule. -
-<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
- <version>${logback-jakarta.version}</version>
+ <version>${logback.version}</version>
</dependency>
-
- reload4j If you wish to use +
reload4j If you wish to use reload4j as the underlying logging framework, all you need to do is to declare "org.slf4j:slf4j-reload4j" as a dependency in your pom.xml file as shown below. In addition to @@ -571,11 +499,10 @@
Declaring project -
log4j 1.2.x As of SLF4J
- version 1.7.36, declaring a dependency on
- org.slf4j:slf4j-log4j12 redirects to
- org.slf4j:slf4j-reload4j by virtue of Maven
- <relocation> directive.
log4j As of version 1.7.35,
+ declaring a dependency on org.slf4j:slf4j-log4j12
+ redirects to org.slf4j:slf4j-reload4j by virtue of
+ Maven <relocation> directive.
<dependency> <groupId>org.slf4j</groupId> @@ -606,28 +533,7 @@- - -Declaring project <version>${latest.stable.version}</version> </dependency>
SLF4J Simple If you - wish to use org.slf4j.simple as the underlying logging - implementation, all you need to do is to declare - "org.slf4j:slf4j-simple" as a dependency in your pom.xml - file as shown below. In addition to - slf4j-simple-${latest.stable.version}.jar, this will - pull in slf4j-api-${latest.stable.version}.jar into - your project. Note that explicitly declaring a dependency on - slf4j-api-${latest.stable.version}.jar is not wrong and - may be necessary to impose the correct version of said artifact - by virtue of Maven's "nearest definition" dependency mediation - rule.
- -<dependency>
- <groupId>org.slf4j</groupId>
- <artifactId>slf4j-simple</artifactId>
- <version>${latest.stable.version}</version>
-</dependency>
-
Binary compatibility
diff --git a/src/site/pages/news.html b/src/site/pages/news.html index 3f21585..263047a 100644 --- a/src/site/pages/news.html +++ b/src/site/pages/news.html @@ -8,12 +8,11 @@ - + - - +SLF4J News
-
2022-09-28 - Release of SLF4J 2.0.3
+2022-09-14 - Release of SLF4J 2.0.1
+ +• The Logger.makeLoggingEventBuilder method
+ semantics has changed so that overriding implementations should now
+ always build a new LoggingEventBuilder instance as
+ appropraiate for the implementation, i.e the logging backend. For
+ more details see SLF4J-560.
• Deprecated unused LoggerFactoryBinder and
+ MarkerFactoryBinder classes. This issue was raised in
+ SLF4J-555 by
+ Witalij Berdinskich who provided the relevant patch.
• The binary of this version can be reproduced by checking + out the tag v_2.0.1 from the source code repository + (GitHub). Release built using Java "18" 2022-03-22 build 18+36-2087 + under Linux Debian 11.2.
+ + ++ +
2022-08-20 - Release of SLF4J 2.0.0
The the 2.0.x series requires Java 8 and adds a backward-compatible 2022-09-28 - Release of SLF4J 2.0.3 href="faq.html#changesInVersion200">detailed in the FAQ page.
-• Fixed a bug in Reload4jLoggerAdapter when
- used in conjunction with the fluent API, the timestamp would not be
- correctly set. This issue was reported
- in SLF4J-546 by
- Joseph Walton.
• The binary of this version can be reproduced by checking - out the tag v_2.0.3 from the source code repository - (GitHub). Release built using Java "19" 2022-09-20 build 19+36-2038 - under Linux Debian 11.2.
- - -- -
2022-09-20 - Release of SLF4J 2.0.2
- -• Fixed bug in the setContextMap() method
- of Reload4jMDCAdapter. This issue was reported
- in SLF4J-563 by
- Michael Wartes.
• The binary of this version can be reproduced by checking - out the tag v_2.0.2 from the source code repository - (GitHub). Release built using Java "18" 2022-03-22 build 18+36-2087 - under Linux Debian 11.2.
- - -- -
2022-09-14 - Release of SLF4J 2.0.1
- -• The Logger.makeLoggingEventBuilder method
- semantics has changed so that overriding implementations should now
- always build a new LoggingEventBuilder instance as
- appropraiate for the implementation, i.e the logging backend. For
- more details see SLF4J-560.
• Deprecated unused LoggerFactoryBinder and
- MarkerFactoryBinder classes. This issue was raised in
- SLF4J-555 by
- Witalij Berdinskich who provided the relevant patch.
• The binary of this version can be reproduced by checking - out the tag v_2.0.1 from the source code repository - (GitHub). Release built using Java "18" 2022-03-22 build 18+36-2087 - under Linux Debian 11.2.
- - -- -
2022-08-20 - Release of SLF4J 2.0.0
-• Except minor javadoc changes, this release is identical to 2.0.0-beta1 released earlier this month.
+ +• The binary of this version can be reproduced by checking out the tag v_2.0.0 from the source code repository @@ -132,7 +102,7 @@
2022-08-20 - Release of SLF4J 2.0.0
-
2022-08-06 - Release of SLF4J 2.0.0-beta1
+2022-08-06 - Release of SLF4J 2.0.0-beta1
• Methods in the LoggingEventBuilder interface
returning an instance of LoggingEventBuilder are now
@@ -160,7 +130,7 @@
2022-08-06 - Release of SLF4J 2.0.0-beta
- 2022-08-05 - Release of SLF4J 2.0.0-beta0
+ 2022-08-05 - Release of SLF4J 2.0.0-beta0
- 2022-01-25 - Release of SLF4J 1.7.34
+2022-01-25 - Release of SLF4J 1.7.34
The relocation element in slf4j-log4j12 had incorrect version number. Version 1.7.34 should not be used.
-2022-01-13 - Release of SLF4J 2.0.0-alpha6
+2022-01-13 - Release of SLF4J 2.0.0-alpha6
• SLF4J now ships with the slf4j-reload4j module
delegating to the reload4j backend. 2022-01-13 - Release of SLF4J 2.0.0-alp
• SLF4J now ships with the slf4j-reload4j module
delegating to the reload4j backend. 2022-01-13 - Release of SLF4J 1.7.33
• The
META-INF/services/java.lang.System$LoggerFinder
@@ -304,7 +274,7 @@ • Added support for the Java Platform Logging API
@@ -315,7 +285,7 @@ In addition to fixes imported from the 1.7 branch, such as SLF4J-515, this
@@ -345,7 +315,7 @@ In the slf4j-simple module, • Fixed important bug in the fluent API. The
In the jcl-over-slf4j module avoid Fixed a memory leak in case of no provided binding and
multithreaded initialization as described in 16th of December, 2019 - Release of SLF4J 1.7
In the pom file for jcl-over-slf4j module, the Apache
license is now explicitly mentioned. In previous versions, the
@@ -431,7 +401,7 @@ • Refactored the fluent-api in
• Added This version had the incorrect "Automatic-Module-Name" for the
@@ -517,7 +487,7 @@ The the 2.0.x series requires Java 8 and
adds a backward-compatible 13th of June, 2019 - Release of SLF4J
Fixed ignored Throwable issue in log4j-over-slf4j as reported in
SLF4J-233 by
@@ -560,7 +530,7 @@ In the 1.8.x series, SLF4J has been
modularized per February 19th, 2019 - Release of SLF4J 1
href="https://jira.qos.ch/browse/SLF4J-454">SLF4J-454.
- Due to popular demand in relation to CVE-2018-8088,
@@ -635,7 +605,7 @@ Automatic module name for the artifact jul-to-slf4j.jar
@@ -665,7 +635,7 @@ Fix Travis build issues as reported in SLF4J-427 by
@@ -686,7 +656,7 @@ Given that the same package name in different modules is a
showstopper in Java 9, the The JPMS module names for Removed spurious System.out.println in the slf4j-log4j12
module. See April 13th, 2017 - Release of SLF4J 1.8
SLF4J has been modularized per JPMS/Jigsaw
@@ -745,7 +715,7 @@ In slf4j-simple module, added a configuration option to
enable/disable caching of the System.out/err target. This
@@ -766,7 +736,7 @@ In its MANIFEST.MF file, the jcl-over-slf4j module now declares
exporting Update to SLF4J version 1.7.23 to enable
slf4j-log4j12 to run under Java 9. Add support for OFF level in Fixed a memory leak due to a race-condition occurring during
SLF4J initialization. In that case, some
@@ -852,7 +822,7 @@ Releases 1.7.19 and 1.7.20 suffer from a memory leak. Please
@@ -868,7 +838,7 @@ Releases 1.7.19 and 1.7.20 suffer from a memory leak. Please
@@ -890,7 +860,7 @@ Initialization of the slf4j-simple module is now thread safe
fixing SLF4J-356.
@@ -904,7 +874,7 @@ When running under Android, skip binding ambiguity check during
initialization for better performance. The fix introduced in version 1.7.14
@@ -913,7 +883,7 @@ The In previous versions of SLF4J, if the application was already
multithreaded at the time the first SLF4J logger was created, logs
@@ -936,7 +906,7 @@ The assignment of the INITIALIZATION_STATE variable in
Fixed All java files have been reformatted to with the code formatter
style defined in codeStyle.xml. This style uses 4 spaces for
@@ -1069,7 +1039,7 @@ The Spot
incorrectly named loggers by setting the
@@ -1112,14 +1082,14 @@ Numerous small code improvements too minor to be listed
here. SFL4J API now uses generics. This enhancement was contributed by
Otavio Garcia. Due to erasure of generics in Java, the changes are
@@ -1133,7 +1103,7 @@ Added slf4j-android module to the slf4j distribution. This
module is contributed by Andrey Korzhevskiy. Given the significance of these performance
improvements, users are highly encouraged to migrate to SLF4J
@@ -1206,14 +1176,14 @@ Added a package private The jul-to-slf4j bridge now correctly handles cases where the
message string contains {}-placeholders but has no or zero
@@ -1229,7 +1199,7 @@ Added osgi-over-slf4j module which serves as an OSGi LogService
implementation delegating to slf4j. This module is maintained by
@@ -1254,7 +1224,7 @@ SLF4J now requires JDK 1.5. Source repository has been moved to https://github.com/qos-ch/slf4j
@@ -1315,7 +1285,7 @@ In the slf4j-log4j12 module, upgraded the log4j dependency to
version 1.2.17. Fixed in thread-safety issues in Fixed bug
@@ -1388,7 +1358,7 @@ Updated log4j dependency to version 1.2.16 and CAL10N dependency to version
@@ -1405,7 +1375,7 @@ It is expected that all SLF4J releases in the 1.6.x
series will be mutually compatible.
diff --git a/src/site/pages/templates/header.js b/src/site/pages/templates/header.js
index e33c689..6998b5e 100644
--- a/src/site/pages/templates/header.js
+++ b/src/site/pages/templates/header.js
@@ -12,38 +12,27 @@ document.write(' ')
//document.write('
- 2022-01-13 - Release of SLF4J 1.7.33
+ 2022-01-13 - Release of SLF4J 1.7.33
- 30th of August, 2021 - Release of SLF4J 2.0.0-alpha5
+ 30th of August, 2021 - Release of SLF4J 2.0.0-alpha5
30th of August, 2021 - Release of SLF4J
- 12th of August, 2021 - Release of SLF4J 2.0.0-alpha4
+ 12th of August, 2021 - Release of SLF4J 2.0.0-alpha4
12th of August, 2021 - Release of SLF4J
- 10th of August, 2021 - Release of SLF4J 2.0.0-alpha3
+ 10th of August, 2021 - Release of SLF4J 2.0.0-alpha3
10th of August, 2021 - Release of SLF4J
- 20th of July, 2021 - Release of SLF4J 1.7.32
+ 20th of July, 2021 - Release of SLF4J 1.7.32
SimpleLogger now caters
for concurrent access. This fixes 20th of July, 2021 - Release of SLF4J 1.7.32<
- 2nd of July, 2021 - Release of SLF4J 2.0.0-alpha2
+ 2nd of July, 2021 - Release of SLF4J 2.0.0-alpha2
LoggingEventBuilder.addArgument(Supplier) method now
@@ -398,7 +368,7 @@ 2nd of July, 2021 - Release of SLF4J 2.
-
18th of June, 2021 - Release of SLF4J 1.7.31
+ 18th of June, 2021 - Release of SLF4J 1.7.31
Object to
String conversion. This issue was reported in 18th of June, 2021 - Release of SLF4J 1.7.31<
- 16th of December, 2019 - Release of SLF4J 1.7.30
+ 16th of December, 2019 - Release of SLF4J 1.7.30
- 31st of October, 2019 - Release of SLF4J 1.7.29
+ 31st of October, 2019 - Release of SLF4J 1.7.29
31st of October, 2019 - Release of SLF4J 1.7.
- October 1st, 2019 - Release of SLF4J 2.0.0-alpha1
+ October 1st, 2019 - Release of SLF4J 2.0.0-alpha1
org.slf4j.Logger interface to ease the work required
@@ -457,7 +427,7 @@ October 1st, 2019 - Release of SLF4J 2
- 10th of August, 2019 - Release of SLF4J 1.7.28
+ 10th of August, 2019 - Release of SLF4J 1.7.28
Automatic-Module-Name in
MANIFEST.MF files in various SLF4J artifacts. This fixes
@@ -507,7 +477,7 @@ 10th of August, 2019 - Release of SLF4J 1.7.2
- 6th of August, 2019 - Release of SLF4J 1.7.27
+ 6th of August, 2019 - Release of SLF4J 1.7.27
6th of August, 2019 - Release of SLF4J 1.7.27
- 13th of June, 2019 - Release of SLF4J 2.0.0-alpha0
+ 13th of June, 2019 - Release of SLF4J 2.0.0-alpha0
- 2019 - Release of SLF4J 1.8.0-beta5
+ 2019 - Release of SLF4J 1.8.0-beta5
2019 - Release of SLF4J 1.8.0-beta5
- February 19th, 2019 - Release of SLF4J 1.8.0-beta4
+ February 19th, 2019 - Release of SLF4J 1.8.0-beta4
February 16th, 2019 - Release of SLF4J 1.7.26
+ February 16th, 2019 - Release of SLF4J 1.7.26
February 16th, 2019 - Release of SLF4J 1.7.26
- 21st of March, 2018 - Release of SLF4J 1.8.0-beta2
+ 21st of March, 2018 - Release of SLF4J 1.8.0-beta2
21st of March, 2018 - Release of SLF4J 1
and SLF4J-431.
January 30th, 2018 - Release of SLF4J 1.8.0-beta1
+ January 30th, 2018 - Release of SLF4J 1.8.0-beta1
January 30th, 2018 - Release of SLF4J 1.
- October 20th, 2017 - Release of SLF4J 1.8.0-beta0
+ October 20th, 2017 - Release of SLF4J 1.8.0-beta0
org.slf4j.impl package has
@@ -701,7 +671,7 @@ October 20th, 2017 - Release of SLF4J 1.
- April 25th, 2017 - Release of SLF4J 1.8.0-alpha2
+ April 25th, 2017 - Release of SLF4J 1.8.0-alpha2
log4j-over-slf4j and
jcl-over-slf4j are now based on the names of the
@@ -722,7 +692,7 @@ April 25th, 2017 - Release of SLF4J 1.8
- April 13th, 2017 - Release of SLF4J 1.8.0-alpha1
+ April 13th, 2017 - Release of SLF4J 1.8.0-alpha1
- April 7th, 2017 - Release of SLF4J 1.8.0-alpha0
+ April 7th, 2017 - Release of SLF4J 1.8.0-alpha0
April 7th, 2017 - Release of SLF4J 1.8.
- March 16th, 2017 - Release of SLF4J 1.7.25
+ March 16th, 2017 - Release of SLF4J 1.7.25
March 16th, 2017 - Release of SLF4J 1.7.25
-
February 23rd, 2017 - Release of SLF4J 1.7.24
+ February 23rd, 2017 - Release of SLF4J 1.7.24
org.apache.commons.logging version "1.2"
@@ -790,7 +760,7 @@ February 23rd, 2017 - Release of SLF4J 1.7.24
- February 15th, 2017 - Release of SLF4J 1.7.23
+ February 15th, 2017 - Release of SLF4J 1.7.23
February 15th, 2017 - Release of SLF4J 1.7.23
- December 13th, 2016 - Release of SLF4J 1.7.22
+ December 13th, 2016 - Release of SLF4J 1.7.22
SimpleLogger. This
feature was requested in December 13th, 2016 - Release of SLF4J 1.7.22
- April 4th, 2016 - Release of SLF4J 1.7.21
+ April 4th, 2016 - Release of SLF4J 1.7.21
April 4th, 2016 - Release of SLF4J 1.7.21
- March 29th, 2016 - Release of SLF4J 1.7.20
+ March 29th, 2016 - Release of SLF4J 1.7.20
March 29th, 2016 - Release of SLF4J 1.7.20
-
March 14th, 2016 - Release of SLF4J 1.7.19
+ March 14th, 2016 - Release of SLF4J 1.7.19
March 14th, 2016 - Release of SLF4J 1.7.19
-
26th of February, 2016 - Release of SLF4J 1.7.18
+ 26th of February, 2016 - Release of SLF4J 1.7.18
26th of February, 2016 - Release of SLF4J 1.7
- 19th of February, 2016 - Release of SLF4J 1.7.17
+ 19th of February, 2016 - Release of SLF4J 1.7.17
19th of February, 2016 - Release of SLF4J 1.7
- 11th of February, 2016 - Release of SLF4J 1.7.16
+ 11th of February, 2016 - Release of SLF4J 1.7.16
MANIFEST.MF file in slf4j-api.jar module was
missing an export statement for the org.slf4j.event
@@ -923,7 +893,7 @@ 11th of February, 2016 - Release of SLF4J 1.7
- 9th of February, 2016 - Release of SLF4J 1.7.15
+ 9th of February, 2016 - Release of SLF4J 1.7.15
9th of February, 2016 - Release of SLF4J 1.7.
- 24th of January, 2016 - Release of SLF4J 1.7.14
+ 24th of January, 2016 - Release of SLF4J 1.7.14
LoggerFactory is now guaranteed to be consistent for
@@ -988,7 +958,7 @@ 24th of January, 2016 - Release of SLF4J 1.7.
- 10th of November, 2015 - Release of SLF4J 1.7.13
+ 10th of November, 2015 - Release of SLF4J 1.7.13
LoggerFactory initialisation problem in
@@ -1033,7 +1003,7 @@ 10th of November, 2015 - Release of SLF4J 1.7
- March 26th, 2015 - Release of SLF4J 1.7.12
+ March 26th, 2015 - Release of SLF4J 1.7.12
March 26th, 2015 - Release of SLF4J 1.7.12
-
6th of January, 2015 - Release of SLF4J 1.7.10
+ 6th of January, 2015 - Release of SLF4J 1.7.10
MDC.putCloseable method now explicitly returns
MDC.MDCloseable instead of the more generic
@@ -1083,7 +1053,7 @@ 6th of January, 2015 - Release of SLF4J 1.7.1
- 16th of December, 2014 - Release of SLF4J 1.7.9
+ 16th of December, 2014 - Release of SLF4J 1.7.9
16th of December, 2014 - Release of SLF4J 1.7.
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.
-
- 4th of April, 2014 - Release of SLF4J 1.7.7
+ 4th of April, 2014 - Release of SLF4J 1.7.7
4th of April, 2014 - Release of SLF4J 1.7.7
-
February 5th, 2014 - Release of SLF4J 1.7.6
+ February 5th, 2014 - Release of SLF4J 1.7.6
February 5th, 2014 - Release of SLF4J 1.7.6
-
25th of March, 2013 - Release of SLF4J 1.7.5
+ 25th of March, 2013 - Release of SLF4J 1.7.5
25th of March, 2013 - Release of SLF4J 1.7.5
-
18th of March, 2013 - Release of SLF4J 1.7.4
+ 18th of March, 2013 - Release of SLF4J 1.7.4
reset() method to
SimpleLoggerFactory for testing purposes.
- 15th of March, 2013 - Release of SLF4J 1.7.3
+ 15th of March, 2013 - Release of SLF4J 1.7.3
15th of March, 2013 - Release of SLF4J 1.7.3
-
11th of October, 2012 - Release of SLF4J 1.7.2
+ 11th of October, 2012 - Release of SLF4J 1.7.2
11th of October, 2012 - Release of SLF4J 1.7.2
- 14th of September, 2012 - Release of SLF4J 1.7.1
+ 14th of September, 2012 - Release of SLF4J 1.7.1
SimpleLogger
@@ -1269,7 +1239,7 @@ 14th of September, 2012 - Release of SLF4J 1.7
- 6th of September, 2012 - Release of SLF4J 1.7.0
+ 6th of September, 2012 - Release of SLF4J 1.7.0
6th of September, 2012 - Release of SLF4J 1.7.
- 11th of June, 2012 - Release of SLF4J 1.6.6
+ 11th of June, 2012 - Release of SLF4J 1.6.6
11th of June, 2012 - Release of SLF4J 1.6.6
-
4th of June, 2012 - Release of SLF4J 1.6.5
+ 4th of June, 2012 - Release of SLF4J 1.6.5
4th of June, 2012 - Release of SLF4J 1.6.5
- October 31st, 2011 - Release of SLF4J 1.6.4
+ October 31st, 2011 - Release of SLF4J 1.6.4
BasicMDCAdapter
fixing bug
@@ -1344,7 +1314,7 @@ October 31st, 2011 - Release of SLF4J 1.6.4
-
October 17th, 2011 - Release of SLF4J 1.6.3
+ October 17th, 2011 - Release of SLF4J 1.6.3
LogEvent class in slf4j-ext module now correctly
passes the event data as a parameter object. This fixes October 17th, 2011 - Release of SLF4J 1.6.3
- August 19th, 2011 - Release of SLF4J 1.6.2
+ August 19th, 2011 - Release of SLF4J 1.6.2
August 19th, 2011 - Release of SLF4J 1.6.2
- July 5th, 2010 - Release of SLF4J 1.6.1
+ July 5th, 2010 - Release of SLF4J 1.6.1
July 5th, 2010 - Release of SLF4J 1.6.1
- May 8th, 2010 - Release of SLF4J 1.6.0
+ May 8th, 2010 - Release of SLF4J 1.6.0
');
+document.write(' ');
+//document.write(' ');
-document.write(' 
');
+document.write(' ');
+
+document.write(' ');
+//document.write(' ');
+document.write(' 
');
+document.write(' ');
-document.write(' | ');
-document.write(' ');
-document.write(' ');
-document.write(' ');
-
-document.write(' ');
-//document.write(' ');
-document.write(' ');
-document.write(' ');
-
-document.write(' ');
-//document.write(' ');
-document.write(' ');
-document.write(' ');
-document.write(' |
');
-document.write(' ');
-document.write(' ){kind=icon} ')
-document.write(' ');
-document.write(' |
');
diff --git a/src/site/pages/templates/left.js b/src/site/pages/templates/left.js
index d33a1ee..75737b5 100644
--- a/src/site/pages/templates/left.js
+++ b/src/site/pages/templates/left.js
@@ -21,11 +21,13 @@ document.write(' logevents');
document.write(' ');
document.write(' JUL');
-document.write(' log4j 1.x (replaced by reload4j)');
+document.write(' Log4j');
document.write(' reload4j');
document.write(' Simple');
-document.write(' ');
+document.write(' ');
document.write(' tinylog');
+document.write(' Log4j 2');
+document.write(' JBoss Logging');
document.write(' ');