My view is that in the absence of regular releases and active development, log4j-api-scala should be abandoned. It is more than 3 years since the 12.0 release of log4j-api-scala. The lib does not appear to be commonly used. There are lots of alternatives open to Scala developers. Slf4j predominates in the Scala community and you can use the Slf4j to Log4j bridge if you want to use Log4j as the logging backend.
scala-logging [1] is a good alternative for anyone who currently uses log4j-api-scala. [1] https://index.scala-lang.org/lightbend-labs/scala-logging On Wed, 13 Sept 2023 at 13:46, Volkan Yazıcı <vol...@yazi.ci> wrote: > > Matt, PJ, shall we migrate `log4j-scala` from sbt to Maven? > > `logging-parent` 10.0.0 ships a great deal of convenience for build+release > of Maven-based projects. I have already migrated `logging-parent`, > `log4j-tools`, `log4j-transform`, `log4j-kotlin`, `log4j-jmx-gui` to this > shared infrastructure. Unless we do certain tricks in sbt that are not > possible via Maven, I would like to match `log4j-scala` with the rest by > migrating it to Maven too.
