+1 to what Michael says Drill is using logback and there has been zero pressure to move to another framework.
On Mon, Nov 11, 2013 at 10:15 PM, Michael Rose <[email protected]>wrote: > I believe when Jon says "log4j" he refers to log4j2. Log4j2 is yet another > successor to log4j, which claims to solve issues in logback. I wasn't able > to discern a difference without log4j's usage of Disruptor (3.x). > > Michael Rose (@Xorlev <https://twitter.com/xorlev>) > Senior Platform Engineer, FullContact <http://www.fullcontact.com/> > [email protected] > > > On Mon, Nov 11, 2013 at 2:41 PM, Patricio Echagüe <[email protected]>wrote: > >> Logback if I'm not wrong was created by the creators of log4j and it's >> more efficient and modern. What would be the rationale to switch to log4j? >> >> Sent from my Nexus 4. >> On Nov 11, 2013 6:14 PM, "P. Taylor Goetz" <[email protected]> wrote: >> >>> No, and I doubt there would be any pressure to switch to log4j. If you >>> look at the logback website[1] there are many Apache projects using it. >>> >>> [1] http://logback.qos.ch >>> >>> >>> On Nov 11, 2013, at 4:09 PM, Jon <[email protected]> wrote: >>> >>> > With the switch of Storm to Apache, are there any plans to move away >>> from Logback?...mainly pressure from Apache to switch to Apache Log4j2? >>> Just curious as this sort of pressures our application to use one logger or >>> another for non-Storm components. >>> >>> >
