SLF4J / SLF4J-561 [Open] SLF4J 1.x to 2.x migration bridge library. ============================== 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-561 ============================== Issue created ------------------------------ Garret Wilson created this issue on 19/Sep/22 6:04 PM Summary: SLF4J 1.x to 2.x migration bridge library. Issue Type: New Feature Assignee: SLF4J developers list Created: 19/Sep/22 6:04 PM Priority: Major Reporter: Garret Wilson Description: Did I read somewhere that there is a SLF4J 2.x compatibility module that will provide {{StaticLoggerBinder}} to keep old applications from breaking? I thought I had read that somewhere, but I can't find it now. If there is no such thing, then I propose that a separate SLF4J 2.x library be published as a sort of "migration bridge" between SLF4J 1.x and SLF4J 2.x. It would provide a minimal {{StaticLoggerBinder}} that doesn't allow _registration_ of any modules, but would implement {{getLoggerFactory()}} to delegate to the default version. This would allow an application to manually pull in SLF4J 2.x, but still not crash when a misbehaving application such as Spark 3.3.0 tries to access {{StaticLoggerBinder}} manually. (See [SPARK-40489|https://issues.apache.org/jira/browse/SPARK-40489].) This would just be a single artifact to include as a dependency to keep legacy classes from breaking. If you're not open to that suggestion, I suppose I could create such a "bridge" as part of my [Clogr|https://clogr.io/], but my first choice would be for it to be part of official SLF4J. Without such a thing, I fear SLF4J 2.x adoption could be slowed. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)