The micro-benchmark testing I wrote to compare Log4j 1 and 2 shows considerable performance gain in favor of Log4j 2. I have only one request for your consideration: simplifying the way to get all loggers in the system and set/reset logging levels for certain loggers. This is very easy to do in Log4j 1, but thanks to the rewrite of API and implementation in Log4j 2, it becomes complicated. I did search and read previous discussions (in August and May) on this topic, and consider this a much needed feature request. Thanks
On Sat, Sep 28, 2013 at 2:44 AM, Ralph Goers <ralph.go...@dslextreme.com>wrote: > I'd prefer to turn this around and ask a couple of questions: > > 1. Why do you need to know the "official release" date? Is something > blocking you from using Log4j 2? > 2. Are you currently using the beta releases? Are you satisfied that it > is production ready in your environment? > > The answers to the questions above are important for us as that is the > basis for us labeling the release 2.0 GA vs 2.0 beta10 (or 2.0 RC1). > > Ralph > > On Sep 27, 2013, at 8:07 AM, Jingdong Sun wrote: > > > Can anyone tell me when the log4j 2 official release will be available? > > > > Thanks. > > Jingdong Sun > > InfoSphere Streams Development > > Phone 507 253-5958 (T/L 553-5958) > > jind...@us.ibm.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > -- Michael
