From c631bd0ab4c9722f8ed939d520396704608ce633 Mon Sep 17 00:00:00 2001 From: Sven Strickroth Date: Sun, 26 Mar 2023 12:41:29 +0200 Subject: [PATCH] Use id instead of (deprecated) name attribute for anchors Signed-off-by: Sven Strickroth --- src/site/pages/codes.html | 38 ++++----- src/site/pages/extensions.html | 6 +- src/site/pages/faq.html | 62 +++++++-------- src/site/pages/legacy.html | 24 +++--- src/site/pages/log4shell.html | 2 +- src/site/pages/manual.html | 26 +++---- src/site/pages/news.html | 136 ++++++++++++++++----------------- 7 files changed, 147 insertions(+), 147 deletions(-) diff --git a/src/site/pages/codes.html b/src/site/pages/codes.html index 4445d18..15cf3b4 100644 --- a/src/site/pages/codes.html +++ b/src/site/pages/codes.html @@ -21,7 +21,7 @@

SLF4J warning or error messages and their meanings

-

No SLF4J providers +

No SLF4J providers were found.

@@ -58,7 +58,7 @@

No SLF4J providers -

Class path contains +

Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier

@@ -88,7 +88,7 @@

Class path contains

IllegalStateException: + id="unsuccessfulInit">IllegalStateException: org.slf4j.LoggerFactory in failed state. Original exception was thrown EARLIER.

@@ -105,7 +105,7 @@

Class path contains -

The method +

The method o.a.commons.logging.impl.SLF4FLogFactory#release was invoked.

@@ -138,7 +138,7 @@

The method -

Operation +

Operation [suchAndSuch] is not supported in jcl-over-slf4j.

@@ -161,7 +161,7 @@

Operation

-

Detected logger +

Detected logger name mismatch

Logger name mismatch warnings are printed only if the @@ -216,7 +216,7 @@

Detected logger -

Failed to load class +

Failed to load class org.slf4j.impl.StaticLoggerBinder

This warning message is reported when the @@ -286,7 +286,7 @@

--> -

Multiple bindings +

Multiple bindings were found on the class path

@@ -358,7 +358,7 @@

Multiple bindings -

slf4j-api version +

slf4j-api version does not match that of the binding

An SLF4J binding designates an artifact such as @@ -392,7 +392,7 @@

slf4j-api version -

Logging factory implementation +

Logging factory implementation cannot be null

This error is reported when the LoggerFactory @@ -405,7 +405,7 @@

Logging factory implementation -

Detected both +

Detected both log4j-over-slf4j.jar AND slf4j-reload4j on the class path, preempting StackOverflowError.

@@ -458,7 +458,7 @@

Detected both -

Detected both +

Detected both jcl-over-slf4j.jar AND slf4j-jcl.jar on the class path, preempting StackOverflowError.

@@ -500,7 +500,7 @@

Detected both

-

Exception in +

Exception in thread "main" java.lang.NoSuchFieldError: tlm

@@ -538,7 +538,7 @@ 
Exception in
     
     
 
-    
Failed to load
+    
Failed to load
     class "org.slf4j.impl.StaticMDCBinder"

     
     
This error indicates that appropriate SLF4J binding could not
@@ -551,7 +551,7 @@ 
Failed to load
 
     
 
-    
MDCAdapter cannot be null 
+    
MDCAdapter cannot be null 
     

 
     
This error is reported when org.slf4j.MDC class
@@ -563,7 +563,7 @@ 
MDCAdapter cannot be null
     
    
 
-    
A number (N) of logging calls
+    
A number (N) of logging calls
     during the initialization phase have been intercepted and are now
     being replayed. These are subject to the filtering rules of the
     underlying logging system.
@@ -583,7 +583,7 @@ 
A number (N) of logging calls
  
     
 
-    
Substitute loggers
+    
Substitute loggers
     were created during the default configuration phase of the
     underlying logging system

 
@@ -616,7 +616,7 @@ 
Substitute loggers
   
     
 
-    
SLF4J versions 1.4.0 and
+    
SLF4J versions 1.4.0 and
     later requires log4j 1.2.12 or later

 
     
The trace level was added to log4j in version 1.2.12 released
@@ -636,7 +636,7 @@ 
SLF4J versions 1.4.0 and
     
 
      
java.lang.NoClassDefFoundError:
+     id="log4j_version">java.lang.NoClassDefFoundError:
      org/slf4j/event/LoggingEvent

 
      
Logback-classic version 1.1.4 and later require slf4j-api
diff --git a/src/site/pages/extensions.html b/src/site/pages/extensions.html
index f33009f..7e2d9a2 100644
--- a/src/site/pages/extensions.html
+++ b/src/site/pages/extensions.html
@@ -26,7 +26,7 @@ 
SLF4J extensions

 
     
 
-		
Profilers

+		
Profilers

 
 		
What is a profiler?

     
@@ -295,7 +295,7 @@ 
Printing using a logger

 
 
 
-   
MDCStrLookup

+   
DCStrLookup

 
    
StrLookup is a class defined in Apache Commons Lang. It is used
    in conjunction with the StrSubstitutor class to allow Strings to
@@ -320,7 +320,7 @@ 
MDCStrLookup

 
 
 
-   
Extended Logger

+   
Extended Logger

 
    
The XLogger
diff --git a/src/site/pages/faq.html b/src/site/pages/faq.html
index 3cac248..f38f7fd 100644
--- a/src/site/pages/faq.html
+++ b/src/site/pages/faq.html
@@ -16,7 +16,7 @@
  

   
 
-  
Frequently Asked Questions about SLF4J

+  
Frequently Asked Questions about SLF4J

 
   
Generalities

   
@@ -190,7 +190,7 @@ 
Frequently Asked Questions about SLF4J

   
Generalities

   
   

-    
What is SLF4J?

+    
What is SLF4J?

     

       
SLF4J is a simple facade for logging systems allowing the
       end-user to plug in the desired logging system at deployment
@@ -198,7 +198,7 @@ 
Generalities

       
      
     

     
-    
When should SLF4J be used?

+    
When should SLF4J be used?

     
     

       
In short, libraries and other embedded components should
@@ -243,7 +243,7 @@ 
Generalities

       
     

     
-    
Is SLF4J yet
+    
Is SLF4J yet
     another logging facade?

     
     

@@ -257,7 +257,7 @@ 
Generalities

       
       
     

-    
If SLF4J fixes JCL,
+    
If SLF4J fixes JCL,
     then why wasn't the fix made in JCL instead of creating a new
     project?
     

@@ -288,7 +288,7 @@ 
Generalities

       
     
     
-    
When using SLF4J, do
+    
When using SLF4J, do
     I have to recompile my application to switch to a different
     logging system?
     

@@ -312,7 +312,7 @@ 
Generalities

       
     
 
-    
What are SLF4J's
+    
What are SLF4J's
     requirements?
     

     
@@ -360,7 +360,7 @@ 
Generalities

     
 
     
-    

+    

       What has changed in SLF4J version 2.0.0?
     

 
@@ -446,7 +446,7 @@ 
Generalities

     
     
 
-    
Are SLF4J versions
+    
Are SLF4J versions
     backward compatible?
     

 
@@ -483,7 +483,7 @@ 
Generalities

 
     
 
-    
I am getting
+    
I am getting
     IllegalAccessError exceptions when using SLF4J. Why
     is that?
     

@@ -535,7 +535,7 @@ 
Generalities

 
     
 
-    
Why is SLF4J licensed under
+    
Why is SLF4J licensed under
     X11 type license instead of the Apache Software License?
     

     
@@ -553,7 +553,7 @@ 
Generalities

     
 
     
-    
Where can I get a
+    
Where can I get a
     particular SLF4J provider/binding?
     

     
@@ -581,7 +581,7 @@ 
Generalities

       
     
     
-    
Should my library
+    
Should my library
     attempt to configure logging?
     

     
@@ -602,7 +602,7 @@ 
Generalities

     
     
 
-    
In order to reduce
+    
In order to reduce
     the number of dependencies of our software we would like to make
     SLF4J an optional dependency. Is that a good idea?      
     

@@ -696,7 +696,7 @@ 
Generalities

 
    
 
-    
What about Maven transitive
+    
What about Maven transitive
     dependencies?
     

     
@@ -743,7 +743,7 @@ 
Generalities

     
     
     
-    
How do I exclude
+    
How do I exclude
     commons-logging as a Maven dependency?
     

     
@@ -870,7 +870,7 @@ 
Generalities

 
     
     
-    
What are the JPMS
+    
What are the JPMS
     module names of the various SLF4J artifacts?
     

     
@@ -926,7 +926,7 @@ 
About the SLF4J API

   
   

     
-    
Why don't the
+    
Why don't the
     printing methods in the Logger interface accept message of type
     Object, but only messages of type String?
     

@@ -983,7 +983,7 @@ 
About the SLF4J API

     
     
 
-    
Can I log an
+    
Can I log an
     exception without an accompanying message?
     

 
@@ -1041,7 +1041,7 @@ 
About the SLF4J API

     
     
     
-    
What is the
+    
What is the
     fastest way of (not) logging?
     

 
@@ -1188,7 +1188,7 @@ 
About the SLF4J API

     
     
     
-    
How can I log the
+    
How can I log the
     string contents of a single (possibly complex) object?

     
     

@@ -1218,7 +1218,7 @@ 
About the SLF4J API

     
     
     
-    
Why doesn't the
+    
Why doesn't the
     org.slf4j.Logger interface have methods for the FATAL
     level?
     

@@ -1280,7 +1280,7 @@ 
About the SLF4J API

     
     
     
-    
Why was the TRACE level
+    
Why was the TRACE level
     introduced only in SLF4J version 1.4.0?

     
     

@@ -1325,7 +1325,7 @@ 
About the SLF4J API

     

 
     
-    
Does the SLF4J logging API
+    
Does the SLF4J logging API
     support I18N (internationalization)?
     

     
@@ -1341,7 +1341,7 @@ 
About the SLF4J API

 
     
 
-    
Is it possible to
+    
Is it possible to
     retrieve loggers without going through the static methods in
     LoggerFactory?
     

@@ -1374,7 +1374,7 @@ 
About the SLF4J API

     
     
 
-    
In the presence of an
+    
In the presence of an
     exception/throwable, is it possible to parameterize a logging
     statement?

 
@@ -1422,7 +1422,7 @@ 
Implementing the SLF4J API

 
     
 
-    
How do I make my
+    
How do I make my
     logging framework SLF4J compatible?
     

     
@@ -1483,7 +1483,7 @@ 
Implementing the SLF4J API

 
     
 
-    
How can my logging
+    
How can my logging
     system add support for the Marker interface?
     

     

@@ -1517,7 +1517,7 @@ 
Implementing the SLF4J API

     
     
 
-    
How does SLF4J's
+    
How does SLF4J's
     version check mechanism work?
     

     
@@ -1574,7 +1574,7 @@ 
General questions about logging

   

 
     
-    
Should Logger members
+    
Should Logger members
     of a class be declared as static?
     

     

@@ -1739,7 +1739,7 @@ 
Explanation

   
   
   

-    
Is there a
+    
Is there a
     recommended idiom for declaring a logger in a class?
     

     
diff --git a/src/site/pages/legacy.html b/src/site/pages/legacy.html
index 59a3e67..c64e299 100644
--- a/src/site/pages/legacy.html
+++ b/src/site/pages/legacy.html
@@ -44,10 +44,10 @@ 
Bridging legacy APIs

     

     

     
-    
Gradual migration to
+    
Gradual migration to
     SLF4J from Jakarta Commons Logging (JCL)

     
-    
jcl-over-slf4j.jar

+    
jcl-over-slf4j.jar

     
     
To ease migration to SLF4J from JCL, SLF4J distributions
     include the jar file jcl-over-slf4j.jar. This jar file is
@@ -72,7 +72,7 @@ 
jcl-over-slf4j.jar

     class loader issues related to commons logging.
     

     
-    
slf4j-jcl.jar

+    
slf4j-jcl.jar

     
     
Some of our users after having switched to SLF4J API realize that
     in some contexts the use of JCL is mandatory and their use of SLF4J
@@ -87,7 +87,7 @@ 
slf4j-jcl.jar

     

     
     
jcl-over-slf4j.jar should not be
+    id="jclRecursion">jcl-over-slf4j.jar should not be
     confused with slf4j-jcl.jar

     
     
@@ -117,7 +117,7 @@ 
slf4j-jcl.jar

     

     
     
-    
log4j-over-slf4j

+    
log4j-over-slf4j

     
     
SLF4J ship with a module called log4j-over-slf4j.  It
     allows log4j users to migrate existing applications to SLF4J without
@@ -126,7 +126,7 @@ 
log4j-over-slf4j

     described below.
     

     
-    
How does it work?

+    
How does it work?

     
     
The log4j-over-slf4j module contains replacements of most widely
     used log4j classes, namely org.apache.log4j.Category,
@@ -156,7 +156,7 @@ 
How does it work?

     href="http://logback.qos.ch/manual/index.html">its manual.
     

     
-    
When does it not work?

+    
When does it not work?

     
     
The log4j-over-slf4j module will not work when the
     application calls log4j components that are not present in the
@@ -170,7 +170,7 @@ 
When does it not work?

 
     
     
-    
What about the
+    
What about the
     overhead?

     
     
The overhead of using log4j-over-slf4j instead of log4j
@@ -187,7 +187,7 @@ 
What about the
     

 
     
     
-    
log4j-over-slf4j.jar
+    
log4j-over-slf4j.jar
     and slf4j-reload4j.jar cannot be present simultaneously
     

     
@@ -217,7 +217,7 @@ 
log4j-over-slf4j.jar
     

 
     
-    
jul-to-slf4j bridge

+    
jul-to-slf4j bridge

     
     
The jul-to-slf4j.jar artifact includes a
     java.util.logging (jul) handler, namely
@@ -257,7 +257,7 @@ 
jul-to-slf4j bridge

     
     
     
-    
jul-to-slf4j.jar and slf4j-jdk14.jar cannot be present
+    
jul-to-slf4j.jar and slf4j-jdk14.jar cannot be present
     simultaneously
     

     
diff --git a/src/site/pages/log4shell.html b/src/site/pages/log4shell.html
index 0471bd2..b6b90d6 100644
--- a/src/site/pages/log4shell.html
+++ b/src/site/pages/log4shell.html
@@ -184,7 +184,7 @@ 
Does a similar vulnerability exist in logback?

       LOGBACK-1591/CVE-2021-42550 are of different severity
       levels.

 
-      
Additional protective
+      
Additional protective
       measure: write protect log4j{1,2}/logback configuration
       files

 
diff --git a/src/site/pages/manual.html b/src/site/pages/manual.html
index 42093fb..46e5147 100644
--- a/src/site/pages/manual.html
+++ b/src/site/pages/manual.html
@@ -26,13 +26,13 @@ 
SLF4J user manual

     the addition of only a single mandatory dependency, namely
     slf4j-api-${latest.stable.version}.jar.

 
-    
Where are the Maven coordinates?

+    
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

+    
Salient historical changes

     
     
since 1.6.0 If no binding is found on the
     class path, then SLF4J will default to a no-operation
@@ -79,7 +79,7 @@ 
Salient historical changes

     details.
     

 
-    
Hello World

+    
Hello World

 
     
As customary in programming tradition, here is an example
     illustrating the simplest way to output "Hello world" using SLF4J.
@@ -135,7 +135,7 @@ 
Hello World

 
      
0 [main] INFO HelloWorld - Hello World

       
-     
Typical usage
+     
Typical usage
      pattern

  
      
The sample code below illustrates the typical usage pattern
@@ -169,7 +169,7 @@ 
Typical usage
 21: }
-

Fluent Logging API

+

Fluent Logging API

since 2.0.0 SLF4J API version 2.0.0 requires Java 8 and introduces a backward-compatible @@ -262,7 +262,7 @@

Fluent Logging API

customizable behaviour.

-

Binding with a logging +

Binding with a logging framework at deployment time

As mentioned previously, SLF4J supports various logging @@ -401,7 +401,7 @@

Binding with a logging find it very easy to write SLF4J bindings.

-

Libraries

+

Libraries

Authors of widely-distributed components and libraries may code against the SLF4J interface in order to avoid imposing a @@ -447,7 +447,7 @@

Libraries

href="faq.html#optional_dependency">dependency reduction and testing.

-

Declaring project +

Declaring project dependencies for logging

Given Maven's transitive dependency rules, for "regular" @@ -616,7 +616,7 @@

Declaring project -

Binary +

Binary compatibility

An SLF4J binding designates an artifact such as @@ -658,7 +658,7 @@

Binary a warning about the suspected mismatch.

-

Consolidate logging via +

Consolidate logging via SLF4J

Often times, a given project will depend on various @@ -672,7 +672,7 @@

Consolidate logging via APIs.

-

Support for JDK Platform Logging (JEP 264) +

Support for JDK Platform Logging (JEP 264) SLF4J

Since 2.0.0-alpha5 The @@ -688,7 +688,7 @@

Support for JDK Platform Logging (JEP 264) -

Mapped Diagnostic Context (MDC) support

+

Mapped Diagnostic Context (MDC) support

"Mapped Diagnostic Context" is essentially a map maintained by the logging framework where the application code provides @@ -718,7 +718,7 @@

Mapped Diagnostic Context (MDC) support

-

Executive summary

+

Executive summary

diff --git a/src/site/pages/news.html b/src/site/pages/news.html index bcf51d5..b52e63a 100644 --- a/src/site/pages/news.html +++ b/src/site/pages/news.html @@ -73,7 +73,7 @@

On the 2.0.x series

-

2023-03-17 - Release of SLF4J 2.0.7

+

2023-03-17 - Release of SLF4J 2.0.7

• Fixed several OSGi MANIFEST.MF related issues, namely SLF4J-581, @@ -101,7 +101,7 @@

2023-03-17 - Release of SLF4J 2.0.7

-

2022-12-12 - Release of SLF4J 2.0.6

+

2022-12-12 - Release of SLF4J 2.0.6

• When replaying events occuring during initialization, the @@ -126,7 +126,7 @@

2022-12-12 - Release of SLF4J 2.0.6

-

2022-11-25 - Release of SLF4J 2.0.5

+

2022-11-25 - Release of SLF4J 2.0.5

• If a SecurityManager is installed, then LoggerFactory will now load providers as a privileged @@ -144,7 +144,7 @@

2022-11-25 - Release of SLF4J 2.0.5

-

2022-11-17 - Release of SLF4J 2.0.4

+

2022-11-17 - Release of SLF4J 2.0.4

• LoggerFactory now uses the class loader that loaded LoggerFactory class itself to find providers of @@ -172,7 +172,7 @@

2022-11-17 - Release of SLF4J 2.0.4

-

2022-09-28 - Release of SLF4J 2.0.3

+

2022-09-28 - Release of SLF4J 2.0.3

• Fixed a bug in Reload4jLoggerAdapter when used in conjunction with the fluent API, the timestamp would not be @@ -188,7 +188,7 @@

2022-09-28 - Release of SLF4J 2.0.3

-

2022-09-20 - Release of SLF4J 2.0.2

+

2022-09-20 - Release of SLF4J 2.0.2

• Fixed bug in the setContextMap() method of Reload4jMDCAdapter. This issue was reported @@ -203,7 +203,7 @@

2022-09-20 - Release of SLF4J 2.0.2

-

2022-09-14 - Release of SLF4J 2.0.1

+

2022-09-14 - Release of SLF4J 2.0.1

• The Logger.makeLoggingEventBuilder method semantics has changed so that overriding implementations should now @@ -225,7 +225,7 @@

2022-09-14 - Release of SLF4J 2.0.1

-

2022-08-20 - Release of SLF4J 2.0.0

+

2022-08-20 - Release of SLF4J 2.0.0

• Except minor javadoc changes, this release is identical to @@ -239,7 +239,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 @@ -267,7 +267,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

• After a long @@ -284,7 +284,7 @@

2022-08-05 - Release of SLF4J 2.0.0-beta
-

2022-03-17 - Release of SLF4J 2.0.0-alpha7

+

2022-03-17 - Release of SLF4J 2.0.0-alpha7

• Mirroring the change in the 1.7.x series, in this release also the "slf4j-log4j12" artifact automatically instructs Maven to @@ -323,7 +323,7 @@

2022-03-17 - Release of SLF4J 2.0.0-alp -

2022-02-08 - Release of SLF4J 1.7.36

+

2022-02-08 - Release of SLF4J 1.7.36

Correct corrupt "Export-Package" declaration in MANIFEST.MF in log4j-over-slf4j module. This @@ -340,7 +340,7 @@

2022-02-08 - Release of SLF4J 1.7.36

-

2022-01-25 - Release of SLF4J 1.7.35

+

2022-01-25 - Release of SLF4J 1.7.35

• In this release, the "slf4j-log4j12" artifact automatically instructs Maven to use the "slf4j-reload4j" artifact @@ -362,13 +362,13 @@

2022-01-25 - Release of SLF4J 1.7.35

Alexander Veit.

-

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

-

2022-01-13 - Release of SLF4J 1.7.33

+

2022-01-13 - Release of SLF4J 1.7.33

• SLF4J now ships with the slf4j-reload4j module delegating to the reload4j backend. 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

• The META-INF/services/java.lang.System$LoggerFinder @@ -411,7 +411,7 @@

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

• Added support for the Java Platform Logging API @@ -422,7 +422,7 @@

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

In addition to fixes imported from the 1.7 branch, such as SLF4J-515, this @@ -452,7 +452,7 @@

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

In the slf4j-simple module, 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

• Fixed important bug in the fluent API. The LoggingEventBuilder.addArgument(Supplier) method now @@ -505,7 +505,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

In the jcl-over-slf4j module avoid 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

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

-

31st of October, 2019 - Release of SLF4J 1.7.29

+

31st of October, 2019 - Release of SLF4J 1.7.29

In the pom file for jcl-over-slf4j module, the Apache license is now explicitly mentioned. In previous versions, the @@ -538,7 +538,7 @@

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

• Refactored the fluent-api in org.slf4j.Logger interface to ease the work required @@ -564,7 +564,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

• Added Automatic-Module-Name in MANIFEST.MF files in various SLF4J artifacts. This fixes @@ -614,7 +614,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

This version had the incorrect "Automatic-Module-Name" for the @@ -624,7 +624,7 @@

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

The the 2.0.x series requires Java 8 and adds a backward-compatible 13th of June, 2019 - Release of SLF4J

-

2019 - Release of SLF4J 1.8.0-beta5

+

2019 - Release of SLF4J 1.8.0-beta5

Fixed ignored Throwable issue in log4j-over-slf4j as reported in SLF4J-233 by @@ -667,7 +667,7 @@

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

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. -

February 16th, 2019 - Release of SLF4J 1.7.26

+

February 16th, 2019 - Release of SLF4J 1.7.26

Due to popular demand in relation to CVE-2018-8088, @@ -742,7 +742,7 @@

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

Automatic module name for the artifact jul-to-slf4j.jar @@ -772,7 +772,7 @@

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

Fix Travis build issues as reported in SLF4J-427 by @@ -793,7 +793,7 @@

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

Given that the same package name in different modules is a showstopper in Java 9, the org.slf4j.impl package has @@ -808,7 +808,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

The JPMS module names for log4j-over-slf4j and jcl-over-slf4j are now based on the names of the @@ -829,7 +829,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

Removed spurious System.out.println in the slf4j-log4j12 module. See April 13th, 2017 - Release of SLF4J 1.8

-

April 7th, 2017 - Release of SLF4J 1.8.0-alpha0

+

April 7th, 2017 - Release of SLF4J 1.8.0-alpha0

SLF4J has been modularized per JPMS/Jigsaw @@ -852,7 +852,7 @@

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

In slf4j-simple module, added a configuration option to enable/disable caching of the System.out/err target. This @@ -873,7 +873,7 @@

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

In its MANIFEST.MF file, the jcl-over-slf4j module now declares exporting org.apache.commons.logging version "1.2" @@ -897,7 +897,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

Update to SLF4J version 1.7.23 to enable slf4j-log4j12 to run under Java 9.

@@ -925,7 +925,7 @@

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

Add support for OFF level in 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

Fixed a memory leak due to a race-condition occurring during SLF4J initialization. In that case, some @@ -959,7 +959,7 @@

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

Releases 1.7.19 and 1.7.20 suffer from a memory leak. Please @@ -975,7 +975,7 @@

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

Releases 1.7.19 and 1.7.20 suffer from a memory leak. Please @@ -997,7 +997,7 @@

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

Initialization of the slf4j-simple module is now thread safe fixing SLF4J-356. @@ -1011,7 +1011,7 @@

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

When running under Android, skip binding ambiguity check during initialization for better performance. The fix introduced in version 1.7.14 @@ -1020,7 +1020,7 @@

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

The MANIFEST.MF file in slf4j-api.jar module was missing an export statement for the org.slf4j.event @@ -1030,7 +1030,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

In previous versions of SLF4J, if the application was already multithreaded at the time the first SLF4J logger was created, logs @@ -1043,7 +1043,7 @@

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

The assignment of the INITIALIZATION_STATE variable in LoggerFactory is now guaranteed to be consistent for @@ -1095,7 +1095,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

Fixed LoggerFactory initialisation problem in @@ -1140,7 +1140,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

All java files have been reformatted to with the code formatter style defined in codeStyle.xml. This style uses 4 spaces for @@ -1176,7 +1176,7 @@

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

The MDC.putCloseable method now explicitly returns MDC.MDCloseable instead of the more generic @@ -1190,7 +1190,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

Spot incorrectly named loggers by setting the @@ -1226,7 +1226,7 @@

16th of December, 2014 - Release of SLF4J 1.7.
-

4th of April, 2014 - Release of SLF4J 1.7.7

+

4th of April, 2014 - Release of SLF4J 1.7.7

SFL4J API now uses generics. This enhancement was contributed by Otavio Garcia. Due to erasure of generics in Java, the changes are @@ -1240,7 +1240,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

Added slf4j-android module to the slf4j distribution. This module is contributed by Andrey Korzhevskiy.

@@ -1293,7 +1293,7 @@

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

Given the significance of these performance improvements, users are highly encouraged to migrate to SLF4J @@ -1313,14 +1313,14 @@

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

Added a package private 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

The jul-to-slf4j bridge now correctly handles cases where the message string contains {}-placeholders but has no or zero @@ -1336,7 +1336,7 @@

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

Added osgi-over-slf4j module which serves as an OSGi LogService implementation delegating to slf4j. This module is maintained by @@ -1361,7 +1361,7 @@

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 @@ -1376,7 +1376,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

SLF4J now requires JDK 1.5.

@@ -1397,7 +1397,7 @@

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

Source repository has been moved to https://github.com/qos-ch/slf4j @@ -1422,7 +1422,7 @@

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

In the slf4j-log4j12 module, upgraded the log4j dependency to version 1.2.17.

@@ -1437,7 +1437,7 @@

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

Fixed in thread-safety issues in BasicMDCAdapter fixing bug @@ -1451,7 +1451,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

Fixed bug @@ -1495,7 +1495,7 @@

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

Updated log4j dependency to version 1.2.16 and CAL10N dependency to version @@ -1512,7 +1512,7 @@

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

It is expected that all SLF4J releases in the 1.6.x series will be mutually compatible.