SLF4J 2.0.19
-
When the fluent API was used with
XLogger/LoggerWrapperin the slf4j-ext module, caller location was incorrectly reported. To correct this,LoggerWrappernow delegatesmakeLoggingEventBuilder()to the wrapped logger so that the application caller can be correctly extracted. This issue was reported in issues/464. -
In
slf4j-api/DefaultLoggingEventBuilder, a failingtoString()invocation on a key-value value, includingStackOverflowError, no longer aborts logging. The builder now substitutes[FAILED toString()], matching the existing behaviour ofMessageFormatterfor message arguments. This issue was reported in issues/448. -
The
isLoggable()method inSLF4JPlatformLoggernow mapsSystem.Logger.Level.ALLandLevel.OFFthe same way aslog(), that is ALL as TRACE and OFF as ERROR, instead of treating both as always loggable. This is a follow-up to the changes introduced in 2.0.17. See issues/430. -
Published JAR files now package each module's own LICENSE.txt under META-INF/. Previously the parent POM copied the repository-root MIT license into every module, so Apache-2.0 modules such as jcl-over-slf4j and log4j-over-slf4j shipped the wrong license text. This issue was reported in issues/465.
-
A bit-wise identical binary of this version can be reproduced by building from source code at commit f0fc3e52a16d5053039495f4f3b64d191508204f associated with the tag v_2.0.19. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.