You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@yazi.ci> on 2023/09/13 12:46:23 UTC
Migrating `log4j-scala` to Maven
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.
Re: Migrating `log4j-scala` to Maven
Posted by Matt Sicker <ma...@musigma.org>.
If those alternative libraries are sufficient facades, then we could consider archiving this. Otherwise, we’ll look into modernizing the build for making more regular releases again.
> On Sep 13, 2023, at 11:04 AM, PJ Fanning <fa...@apache.org> wrote:
>
> 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ı <vo...@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.
Re: Migrating `log4j-scala` to Maven
Posted by PJ Fanning <fa...@apache.org>.
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ı <vo...@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.