On Tue, 2017-05-02 at 14:21 -0700, Gary Gregory wrote:
> Hi Oleg,
> 
> I updated the documentation for Log4j 2.
> 
> Note that I am unsure on some of the logger names since so much of
> the packaging has changed from 4 to 5. In fact, I left most of the
> logger names in the JUL example section as is.
> 
> Can you review please?
> 

Sure. Log4j2 bits looks OK to me. I'll work on the JUL bits. What is
still missing though is a bit on slf4j configuration. Probably just one
sentence about the slf4j binding and its group and artifact ids.

Oleg


> Thank you,
> Gary
> 
> 
> On Mon, May 1, 2017 at 9:05 AM, Gary Gregory <[email protected]>
> wrote:
> > I'd be happy to.
> > 
> > Gary
> > 
> > 
> > On May 1, 2017 7:43 AM, "Oleg Kalnichevski" <[email protected]>
> > wrote:
> > Gary,
> > 
> > I think it should take me another week or two at most to prepare
> > HttpClient 5.0a2 and put it on vote.
> > 
> > I anticipate there will likely be a lot of people unhappy about us
> > replacing Commons Logging with log4j2 instead of slf4j. 
> > 
> > I think it would help a lot to preempt such criticism by preparing
> > a
> > document or updating our existing logging guide [1] with a simple
> > statement as to why log4j2 has been chosen over slf4j and
> > explaining
> > how log4j2 API can act as a logging facade to other logging
> > toolkits
> > much like slf4j and how logging appenders could be redirected to
> > slf4j
> > APIs.
> > 
> > Would you have some spare cycles to look into that?
> > 
> > 
> > Oleg
> > 
> > [1] http://hc.apache.org/httpcomponents-client-5.0.x/logging.html
> > 
> > 
> > 
> > 
> 
> 
> 
> -- 
> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to