Well said Hen, big +1 :) > > B) If you are an app, use log4j. or logback, depending on the cases, IMHO >
Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Fri, Aug 5, 2011 at 8:18 AM, Henri Yandell <flame...@gmail.com> wrote: > On Wed, Aug 3, 2011 at 7:51 AM, Gary Gregory <garydgreg...@gmail.com> wrote: >> On Wed, Aug 3, 2011 at 10:33 AM, Paul Benedict <pbened...@apache.org> wrote: >>> I prefer Apache driven projects when possible. If LOG4J2 takes off, >>> feature requests would be implemented quicker, I hope. >> >> I like Log4J just fine thank you very much :) >> >> I'm looking forward to 2.0. > > That's generally where I am thought-wise. > > A) If you're a generic reusble library; don't do logging if you can help it. > B) If you are an app, use log4j. > C) If you truly need a bridge, use SLF4j. > > Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
