Seconded on Log4j 2. It provides an API that is also compatible with other
logging implementations besides Log4j 2, so you are not locked into using
On 14 October 2016 at 03:30, Gary Gregory <garydgreg...@gmail.com> wrote:
> Apache Log4j 2 is the preferred migration path IMO.
> Log4j 2 provides a clean separation between API and implementation and a
> ton of powerful features. Version 2.7 was just released.
> On Fri, Oct 14, 2016 at 12:14 AM, Christian Effertz <
> christian.effe...@web.de> wrote:
> > Hello,
> > we support several applications that rely on Apache Commons Logging and
> > Log4j as implementation. After some years we got the budget to polish
> > So we are currently considering how to update the logging framework those
> > applications use. Log4j apparently received an update in recent time,
> > whereas Commons Logging is unchanged since 2014.
> > So we are wondering if it would be a good idea to (a) propose pull
> > via GitHub or (b) to migrate away from Commons Logging.
> > Probably option (b) is the wiser choice as there has been a similar
> > discussion in the related Jira Project,
> > https://issues.apache.org/jira/browse/LOGGING-136.
> > Any official or unofficial comments and thoughts on this topic?
> > Regards
> > Christian Effertz
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> JUnit in Action, Second Edition
> Spring Batch in Action
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
Matt Sicker <boa...@gmail.com>