Re: [logging][proposal] Statement of intent/status

2016-10-17 Thread Bruno P. Kinoshita
+1 and examples on how to migrate from [logging] to log4j2 Thanks Gary Bruno > > From: Gary Gregory >To: Commons Developers List >Sent: Tuesday, 18 October 2016 6:45 AM >Subject: [logging][proposal] Statement of intent/status > > >H

Re: [logging][proposal] Statement of intent/status

2016-10-17 Thread Matt Sicker
+1, recommend log4j2. On 17 October 2016 at 12:56, Stian Soiland-Reyes wrote: > +1 - we can show how Commons Logging user code can be updated to log4j2. > > I think many users of Commons Logging now is through the libraries they > depend on. > > On 17 Oct 2016 6:45 pm, "Gary Gregory" wrote: > >

Re: [logging][proposal] Statement of intent/status

2016-10-17 Thread Stian Soiland-Reyes
+1 - we can show how Commons Logging user code can be updated to log4j2. I think many users of Commons Logging now is through the libraries they depend on. On 17 Oct 2016 6:45 pm, "Gary Gregory" wrote: > Hi All, > > I propose that we state that: > - Apache Commons Logging is entering maintenanc

[logging][proposal] Statement of intent/status

2016-10-17 Thread Gary Gregory
Hi All, I propose that we state that: - Apache Commons Logging is entering maintenance mode: No new features, only maintenance or fixes. - Log4j 2 with it's clean separation of API and implementation modules supersedes Commons Logging. You can code to an API in Log4j2 just like you can in Commons