GitHub user hygt added a comment to the discussion: Deprecate the Log4j Scala API
Hello. I believe I've seen my share of Scala codebases in the past 10+ years, across multiple employers and most of the popular stacks or frameworks (Play, Akka, Spark, Flink, functional ecosystems, ... basically anything not too exotic) First, log4j2 is rarely used as the logging backend. Many projects tend to default to logback. People who look into logging more seriously would pick a more idiomatic and native Scala backend as we have pretty awesome ones. Two exceptions spring to mind: - sbt, which defines its own logging interface - Spark and Flink, they don't use the Scala API As for `log4j-api-scala` it seems the only reverse dependency is Scalaxb. I'm not sure to understand why exactly, maybe it's worth asking @eed3si9n ? You're absolutely right about the widespread usage of macro-based frontends. And Lightbend's Scala logging isn't the only one. GitHub link: https://github.com/apache/logging-log4j2/discussions/4021#discussioncomment-15456188 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
