I'd be a little worried about switching to log4j 2. Two of the main targets of this library when it was proposed were Spark and Hadoop, both of which do not use log4j 2; you might be able to configure them too, but Spark at least has functionality built on top of log4j 1.2, and I'm not sure how well it works with v2 at all.
I'm totally for the idea of not logging, though. On Mon, Jun 6, 2016 at 7:00 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > Hi All: > > IMO. if [crypto] is to have a dependency on a logging framework, it should > be Log4j 2, not Commons Logging. Log4j 2 has an API module, which you can > pair with any number of implementations: Log4j's own Core, JUL, SLF4J, and > so on. > > Gary > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory -- Marcelo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
