November 2022 - slf4j-dev - mailman3.qos.ch

Release of SLF4J version 2.0.4
by Ceki Gülcü 17 Nov '22

17 Nov '22

Hello All, I am very pleased to announce the release of SLF4J version 2.0.4. In this release, LoggerFactory uses the class loader that loaded LoggerFactory class itself to find providers of type SLF4JServiceProvider. Previously, the thread context class loader was used. This was unintentional and the current behavior more closely matches that of the SLF4J 1.7 series and earlier. Please refer to the the news page for more details on this release: http://www.slf4j.org/news.html The 2.0.x series introduces a backward-compatible fluent logging API. By backward-compatible, we mean that existing logging frameworks do not have to be changed in order for the user to benefit from the fluent logging API. However, existing frameworks *must* migrate to the ServiceLoader mechanism. The resulting internal changes are detailed in the FAQ page. http://www.slf4j.org/faq.html#changesInVersion200 The 2.0.x series builds upon the the 1.8.x series which was modularized per Java Platform Module System (JPMS/Jigsaw). The 2.0.x series requires Java 8. Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J provider can cause problems. For example, if you are using slf4j-api-2.0.0.jar, then you should also use slf4j-simple-2.0.0.jar, using slf4j-simple-1.5.5.jar will not work. With the exception of the fluent API (new in SLF4J 2.0.x), from the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your provider matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its provider match, you should be fine. Donations and sponsorship You can also support SLF4J/logback/reload4j projects via donations and sponsorship. We thank our current supporters and sponsors for their continued contributions. Sponsorship link: https://github.com/sponsors/qos-ch Announcement mailing list: You can receive SLF4J/logback/reload4j related announcements by subscribing QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki Gülcü -- Ceki Gülcü Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

1 0

[JIRA] Updates for SLF4J-544: LoggerFactory only loads services from context class loader
by QOS.CH (JIRA) 17 Nov '22

17 Nov '22

SLF4J / SLF4J-544 [Resolved] LoggerFactory only loads services from context class loader ============================== Here's what changed in this issue in the last few minutes. There are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-544 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 17/Nov/22 8:58 PM Resolution: Fixed (was: Duplicate) Status: Resolved (was: Resolved) ============================== 1 comment ------------------------------ Ceki Gülcü on 17/Nov/22 9:01 PM Solved in [commit 43a363|https://github.com/qos-ch/slf4j/commit/43a36303e5] ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-548: Loading services (plugins) with the caller's ClassLoader
by QOS.CH (JIRA) 17 Nov '22

17 Nov '22

SLF4J / SLF4J-548 [Resolved] Loading services (plugins) with the caller's ClassLoader ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-548 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 17/Nov/22 8:56 PM Resolution: Duplicate Status: Resolved (was: Open) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-544: LoggerFactory only loads services from context class loader
by QOS.CH (JIRA) 14 Nov '22

14 Nov '22

SLF4J / SLF4J-544 [Resolved] LoggerFactory only loads services from context class loader ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-544 ============================== 1 comment ------------------------------ Ceki Gülcü on 14/Nov/22 6:56 PM [~ichttt] [~benarnold] Thank you for you feedback. SLF4J was created to solve the classloading problems encountered with Jakarta Commons Logging and its dynamic discovery mechanism. Hence the purposefully dumb static binding mechanism that prevailed in SLF4J version 1.7.x and earlier. The current discovery mechanism which uses the thread context class loader is a involuntary mistake. It will be reverted to the behavior you suggest, that is, using the loader that loaded LoggerFactory. A more flexible loading mechanism may follow in future releases... ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-572: enhance manifest with manual capabilities
by QOS.CH (JIRA) 14 Nov '22

14 Nov '22

SLF4J / SLF4J-572 [Resolved] enhance manifest with manual capabilities ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-572 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 14/Nov/22 6:46 PM Resolution: Fixed Status: Resolved (was: In Progress) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-544: LoggerFactory only loads services from context class loader
by QOS.CH (JIRA) 14 Nov '22

14 Nov '22

SLF4J / SLF4J-544 [Resolved] LoggerFactory only loads services from context class loader ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-544 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 14/Nov/22 6:21 PM Resolution: Duplicate Status: Resolved (was: Open) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-544: LoggerFactory only loads services from context class loader
by QOS.CH (JIRA) 14 Nov '22

14 Nov '22

SLF4J / SLF4J-544 [Open] LoggerFactory only loads services from context class loader ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-544 ============================== 1 comment ------------------------------ Ralph Goers on 14/Nov/22 4:49 PM FWIW, Log4j 2 locates all the ClassLoaders it can reach and calls ServiceLoader for each of them. Unfortunately, that seems to be the only way to work around the ServiceLoader limitations until that application is using JPMS. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-544: LoggerFactory only loads services from context class loader
by QOS.CH (JIRA) 14 Nov '22

14 Nov '22

SLF4J / SLF4J-544 [Open] LoggerFactory only loads services from context class loader ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-544 ============================== 1 comment ------------------------------ Benedikt Arnold on 14/Nov/22 12:29 PM Hi! We have a couple of google cloud functions using slf4j. While some of our dependencies started using slf4j 2.0.x we noticed that logging in our functions is broken. I've created a small example to reproduce this issue locally by using google cloud function invoker. [https://github.com/benediktarnold/slf4j-cloudfunction] The repo has two branches 1. main using slf4j 1.7.36 (logging works as expected) 2. slf4j-2.0 with slf4j 2.0.3 (SLF4J: No SLF4J providers were found.) I've already fixed it locally using the proposal in the tickets description by using an additional ServiceLoader.load call with the class loader of LoggerFactory. Still got some failing tests, but I could try to fix that and create a PR for it. Regards, Ben ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-371: Support the lambda expression in the Logger
by QOS.CH (JIRA) 13 Nov '22

13 Nov '22

SLF4J / SLF4J-371 [Resolved] Support the lambda expression in the Logger ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-371 ============================== 1 comment ------------------------------ Ceki Gülcü on 13/Nov/22 7:58 PM [~ondrej.zizka] The fluent API introduces very little if any overhead for disabled log statements. SLF4J does not support the method mentioned in your comment above. What went wrong in your attempt to migrate to SLF4J 2.0? Are you using Spring Boot? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-371: Support the lambda expression in the Logger
by QOS.CH (JIRA) 10 Nov '22

10 Nov '22

SLF4J / SLF4J-371 [Resolved] Support the lambda expression in the Logger ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-371 ============================== 1 comment ------------------------------ Ondrej Zizka on 10/Nov/22 6:48 PM Hi, I'm late to the heated debate. I want to improve performance and relieve the app of the computation of the params to log calls, while keeping the code minimal. I.e. I prefer not to introduce fluent. 1) Does SLF4J support such simplest lambdas (this is a Kotlin syntax): {code:java} log.debug { "Foo ${bar.expensiveCall()}" } {code} Just so, no format, no additinal calls to fluent wrappers. Note: Kotlin can pass a lambda as both Callable or Supplier params. 2) If yes: Is it natively? Since 2.x? 3) I'm on 1.7.36. 1.7.x is not getting that in any way? 2.x would require migration which I did not figure out on the first try. 4) If not: Is there a plan for that? And is there a 3rd party project allowing that? Thanks! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0