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

[JIRA] Updates for SLF4J-564: SimpleLogger: handleNormalizedLoggingCall has outdated javadoc
by QOS.CH (JIRA) 21 Sep '22

21 Sep '22

SLF4J / SLF4J-564 [Open] SimpleLogger: handleNormalizedLoggingCall has outdated javadoc ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-564 ============================== Issue created ------------------------------ Witalij Berdinskich created this issue on 21/Sep/22 9:05 PM Summary: SimpleLogger: handleNormalizedLoggingCall has outdated javadoc Issue Type: Bug Affects Versions: 2.0.1 Assignee: SLF4J developers list Components: slf4j-simple Created: 21/Sep/22 9:05 PM Labels: documentation Priority: Major Reporter: Witalij Berdinskich Description: Actual parameters are level, marker, messagePattern, arguments, (Throwable) t. Javadoc describes level, message, t ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-447: Slf4j-ext contains package org.slf4j
by QOS.CH (JIRA) 21 Sep '22

21 Sep '22

SLF4J / SLF4J-447 [Open] Slf4j-ext contains package org.slf4j ============================== 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-447 ============================== 1 comment ------------------------------ Mirko Strüßmann on 21/Sep/22 5:14 PM This seems to lead to an error that I am observing when using slf4j with jlink: "Error: Modules slf4j.ext and org.slf4j export package org.slf4j" I would be glad if this issue would be resolved in a coming release. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-563: Reload4jMDCAdapter.setContextMap does not work correctly in 2.0
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-563 [Resolved] Reload4jMDCAdapter.setContextMap does not work correctly in 2.0 ============================== 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-563 ============================== 1 comment ------------------------------ Michael Wartes on 21/Sep/22 1:04 AM Thank you for the fix! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-563: Reload4jMDCAdapter.setContextMap does not work correctly in 2.0
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-563 [Resolved] Reload4jMDCAdapter.setContextMap does not work correctly in 2.0 ============================== 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-563 ============================== 1 comment ------------------------------ Ceki Gülcü on 20/Sep/22 9:54 PM [~mwartes] Thank you for this report and analysis. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-563: Reload4jMDCAdapter.setContextMap does not work correctly in 2.0
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-563 [Resolved] Reload4jMDCAdapter.setContextMap does not work correctly in 2.0 ============================== 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-563 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 20/Sep/22 9:33 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-561: SLF4J 1.x to 2.x migration adapter library.
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-561 [Resolved] SLF4J 1.x to 2.x migration adapter library. ============================== 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-561 ============================== 1 comment ------------------------------ Ceki Gülcü on 20/Sep/22 7:57 PM [~garretwilson] Thank you for letting me know. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-561: SLF4J 1.x to 2.x migration adapter library.
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-561 [Resolved] SLF4J 1.x to 2.x migration adapter library. ============================== 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-561 ============================== 1 comment ------------------------------ Garret Wilson on 20/Sep/22 3:12 PM Ceki if you ever decide to mention this workaround in any documentation, note that I just released a new version with a new artifact name: {{io.clogr:slf4j1-shim:0.8.3}}. I renamed it to indicate that it doesn't require Clogr to work, and "shim" perhaps better described the role it's playing. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-561: SLF4J 1.x to 2.x migration adapter library.
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-561 [Resolved] SLF4J 1.x to 2.x migration adapter library. ============================== 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-561 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 20/Sep/22 12:11 PM Resolution: Won't Fix Status: Resolved (was: Open) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-561: SLF4J 1.x to 2.x migration adapter library.
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-561 [Open] SLF4J 1.x to 2.x migration adapter library. ============================== 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-561 ============================== 1 comment ------------------------------ Ceki Gülcü on 20/Sep/22 11:45 AM [~garretwilson] Thank for doing this. I should mention that SLF4J does take into account StaticLoggerBinder classes found on the class path for reasons of clarity. The solution to the migration is simple, the end-user places a logging backend on the classpath or the module path as appropriate for the version of slf4j-api in user. Also note that JMPS does not allow modules to occupy the same package space. Thus, we know for sure that StaticLoggerBinder will not work in a modular environment. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-561: SLF4J 1.x to 2.x migration adapter library.
by QOS.CH (JIRA) 20 Sep '22

20 Sep '22

SLF4J / SLF4J-561 [Open] SLF4J 1.x to 2.x migration adapter library. ============================== 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-561 ============================== 1 comment ------------------------------ Garret Wilson on 20/Sep/22 5:04 AM I went ahead and implemented this with the [Clogr SLF4J 1.x Adapter|https://github.com/globalmentor/clogr/tree/master/clogr-slf4j1-adap…] which I just published to Maven Central. Now if you're running an application such as Spark which breaks SLF4J 2.x because it accesses {{StaticLoggerBinder}}, just include {{io.clogr:clogr-slf4j1-adapter:0.8.2}}, and the application will magically stop breaking: {code:xml} <dependency> <groupId>io.clogr</groupId> <artifactId>clogr-slf4j1-adapter</artifactId> <version>0.8.2</version> </dependency> {code} This way you can specify the latest SLF4J 2.x libraries as dependencies, and simply adding the {{io.clogr:clogr-slf4j1-adapter}} dependency will function as a stop-gap adapter until the application gets fixed to not rely on {{StaticLoggerBinder}}. This really belongs in the SLF4J libraries, so as soon as you implement this ticket and provide a solution as part of SLF4J, I'll remove {{io.clogr:clogr-slf4j1-adapter}} from future Clogr releases so we won't have competing workarounds. But for now it's the only thing to keep Spark and probably many other applications from breaking with SLF4J 2.x. My only other option right now would be to switch back to SLF4J 1.x, which I'm sure everyone agrees is not desirable. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0