diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html index a205e78a..32bde441 100755 --- a/slf4j-site/src/site/pages/manual.html +++ b/slf4j-site/src/site/pages/manual.html @@ -242,7 +242,8 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail pairs as separates objects. The default implementation as shipping in the org.slf4j.Logger class prefixes key-value pairs to the message. Logging - backends are free to customize the output as they see fit.

+ backends are free and even encouraged to offer a more + customizable behaviour.

Binding with a logging diff --git a/slf4j-site/src/site/pages/news.html b/slf4j-site/src/site/pages/news.html index fe018d5d..847cfd8f 100755 --- a/slf4j-site/src/site/pages/news.html +++ b/slf4j-site/src/site/pages/news.html @@ -44,6 +44,26 @@

XXth of June, 2021 - Release of SLF4J 2.0.0-alpha2

+

The the 2.0.x series requires Java 8 and + adds a backward-compatible fluent logging api. +

+ Moreover, SLF4J has been modularized per JPMS/Jigsaw + specificaton. The resulting internal changes are detailed in the FAQ + page. +

+ +

SLF4J version 2.0.0 requires Java 8. It builds upon the 1.8.x + series and adds a backward-compatible fluent logging api. By + backward-compatible, we mean that existing logging frameworks do + not have to be changed for the user to benefit from the fluent + logging API. +

+ +

Fixed important bug in the fluent API. The LoggingEventBuilder.addArgument(Supplier) method now takes Supplier<?> and not @@ -100,33 +120,16 @@

October 1st, 2019 - Release of SLF4J 2.0.0-alpha1

-

The the 2.0.x series requires Java 8 and - adds a backward-compatible fluent logging api. -

- Moreover, SLF4J has been modularized per JPMS/Jigsaw - specificaton. The resulting internal changes are detailed in the FAQ - page. -

- -

SLF4J version 2.0.0 requires Java 8. It builds upon the 1.8.x - series and adds a backward-compatible fluent logging api. By - backward-compatible, we mean that existing logging frameworks do - not have to be changed for the user to benefit from the fluent - logging API. -

• Refactored the fluent-api in org.slf4j.Logger interface to ease the work required by downstream implementations.

-

• By default, when using the fluent-API +

By default, when using the fluent-API org.slf4j.Logger will merge into the message part any - marker and key-value data passed to it.

+ marker and key-value data passed to it. Non default implementation + are encouraged to implement a more customizable behavior.

• Fix the double back-end initializatoin problem reported in SLF4J-463 by