Here is what I am thinking. I will make the branch tomorrow and put just the minimal changes in place with the modified StatusLogger api. This way when I fix things completely we won't have a breaking api change after 2.0 release. If you like it, we can put just that in trunk and release. On Jul 12, 2014 4:03 PM, "Bruno Mahé" <[email protected]> wrote:
> Hi, > > We have been testing Apache Log4j 2.0rc2 at Tango for a few weeks and have > been very impressed. > We are in the process of migrating our services to Apache Log 2.0rc2 so > they can be ready for roll out when 2.0 comes out. > > The only issue we had so far was about configuring async logger for all > loggers. Having to pass system properties to Apache Tomcat in order to > activate and configure async loggers is not convenient. > > There is also a more detailed email/blog post with some numbers we > collected being worked on. > > Thanks, > Bruno > > On 07/11/2014 05:50 AM, Matt Sicker wrote: > > Do it! Can't wait! Then I'll be able to upgrade from 1.2 at work. :) > > > On 11 July 2014 03:58, Remko Popma <[email protected]> wrote: > >> No objection at all! >> >> I would like to add the tool to generate Custom/Extended Loggers, and do >> a doc fix for LOG4J2-631. >> >> Also, the site now has an empty section "Custom Plugins" under manual > >> Extending Log4j. Shall we remove that before the release? >> >> Sent from my iPhone >> >> > On 2014/07/11, at 15:50, Ralph Goers <[email protected]> >> wrote: >> > >> > I would like to do the release for Log4j 2.0 this weekend. Are there >> any objections? >> > >> > Ralph >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Matt Sicker <[email protected]> > > >
