bpholt commented on issue #2065: URL: https://github.com/apache/logging-log4j2/issues/2065#issuecomment-1845663065
> Reverting https://github.com/apache/logging-log4j2/pull/1920 would only move the problem from log4j-slf4j-impl to log4j-slf4j2-impl, so it is not an option. As you can use on [MvnRepository](https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-slf4j2-impl/2.21.1) (that must be using Scala), before 2.22.0 it was log4j-slf4j2-impl that had the same problem as you have. It's definitely a problem, but IMO a little less severe than the log4j1 artifact, because it works to specify the slf4j 2.x version (directly or transitively): ```scala libraryDependencies ++= Seq( "org.slf4j" % "slf4j-api" % "2.0.9", "org.apache.logging.log4j" % "log4j-slf4j2-impl" % "2.21.0", ) ``` ``` sbt:log4j2-slf4j> evicted [warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible: [warn] * org.slf4j:slf4j-api:2.0.9 is selected over 1.7.36 [warn] +- default:log4j2-slf4j_2.12:0.1.0-SNAPSHOT (depends on 2.0.9) [warn] +- org.apache.logging.log4j:log4j-slf4j2-impl:2.21.0 (depends on 1.7.36) [success] Total time: 0 s, completed Dec 7, 2023, 10:29:56 AM sbt:log4j2-slf4j> show fullClasspath [info] * Attributed(~/log4j2-slf4j/target/scala-2.12/classes) [info] * Attributed(~/.sbt/boot/scala-2.12.18/lib/scala-library.jar) [info] * Attributed(~/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/slf4j/slf4j-api/2.0.9/slf4j-api-2.0.9.jar) [info] * Attributed(~/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/logging/log4j/log4j-slf4j2-impl/2.21.0/log4j-slf4j2-impl-2.21.0.jar) [info] * Attributed(~/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.21.0/log4j-api-2.21.0.jar) [info] * Attributed(~/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/2.21.0/log4j-core-2.21.0.jar) [success] Total time: 0 s, completed Dec 7, 2023, 10:30:07 AM ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
