I thought about that, but it seemed more prudent to try to get people using other frameworks to consolidate on using Log4j and not the other way around.
Ralph On Jul 18, 2014, at 1:40 PM, Matt Sicker <[email protected]> wrote: > But what if I'm still using Java 1.2? :P > > > On 18 July 2014 15:37, Ralph Goers <[email protected]> wrote: > Commons Logging’s purpose is to provide a common API that can sit in front of > any logging implementation. The Log4j API isn’t intended for that. We have > bridges that allow applications written using other APIs to use Log4j 2 as > the implementation. We do have a bridge from the Log4j 2 API to SLF4J, but > that is the only one. As such, I don’t see it as a replacement - at least > not yet. > > Ralph > > > > On Jul 18, 2014, at 1:23 PM, Gary Gregory <[email protected]> wrote: > >> Should we consider proposing that, at least conceptually, Commons Logging be >> deprecated in favor of Log4j 2? >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> 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 <[email protected]>
