I’d be +1 for Log4j2 as the API particularly due to the more active development community and licensing. SLF4J is mostly reliant on the heroic efforts of its sole maintainer which is a bit of an anti-pattern at Apache. If there’s a desire to support the Java module system, the only versions of SLF4J that properly support them are still in alpha or beta releases right now.
> On Nov 22, 2021, at 08:05, Gilles Sadowski <gillese...@gmail.com> wrote: > > Hello. > > Le lun. 22 nov. 2021 à 13:50, Avijit Basak <avijit.ba...@gmail.com> a écrit : >> >> Hi All >> >> We need to make a decision on usage of a logging framework. The >> previous release does not have any implementation of a logging framework. >> However, in the current implementation a slf4j logger has been introduced. >> Please share if anyone has any concerns related to this. > > +1 for using > * the (de-facto standard) SFL4J _interfaces_ [1] in the "src" part of the > GA module, > * Log4j2 [2] implementations in the "test" part of the GA module (and in > the example applications). > > Best, > Gilles > > [1] http://www.slf4j.org/ > [2] https://logging.apache.org/log4j/2.x/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
