blogged! and plus'ed :)
https://blogs.apache.org/logging/entry/apache_log4j_2_0_beta6

On Sun, May 12, 2013 at 8:09 AM, Ralph Goers <[email protected]> wrote:
> The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta6 release!
>
> Apache log4j is a well known framework for logging application behavior. 
> Log4j 2 is an upgrade to
> Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
> and provides
> many of the improvements available in Logback while fixing some inherent 
> problems in Logback's
> architecture.
>
> This is the eighth release of Log4j 2 and is being made available to 
> encourage use and feedback from the community.
>
> Bug fixes and enhancements
>
> Changes in this version include:
>
>
> Fixed Bugs:
> o LOG4J2-231:  Logger.getParent() was not returning the correct Logger.
> o LOG4J2-201:  Renamed Plugin annotation attribute from "type" to "category".
> o LOG4J2-219:  Fix: install default root logger if not configured (this is 
> unchanged),
>         but make sure to include configured named loggers. Clarified 
> documentation. Thanks to Peter DePasquale.
> o LOG4J2-159:  Use OSGi version format in Fragment-Host
> o LOG4J2-234:  RegexFilter threw a NullPointerException when used as a 
> context-wide filter.
> o LOG4J2-192:  Add support for interpolating Environment variables when 
> processing the configuration.
> o LOG4J2-235:  Removed dependency on tools jar from core module, made 
> jconsole dependency optional. Thanks to Sebastian Oerding.
> o LOG4J2-233:  Fixed link to log4j-user mailing list.
> o LOG4J2-222:  Disruptor will now shutdown during Tomcat shutdown. Thanks to 
> Steven Yang.
> o LOG4J2-224:  The FlumeAppender failed to start if the Flume RPCClient could 
> not connect to any Flume agents.
> o LOG4J2-223:  Fix LoggerContext start and stop to eliminate 
> IllegalStateException and NoClassDefFound errors.
> o LOG4J2-221:  Remove hundreds of compiler warnings. Thanks to Nick Williams.
> o LOG4J2-215:  Various small documentation fixes.
> o LOG4J2-217:  Ensure PluginManager streams are always closed. Thanks to 
> Fabien Sanglard.
>
> Changes:
> o LOG4J2-237:  Moved JMX Client GUI classes into separate jmx-gui submodule.
> o LOG4J2-230:  Improved error reporting when misconfigured. Thanks to 
> Wojciech Zaręba.
> o Renamed AsynchAppender to AsyncAppender. Plugin name became Async (was 
> Asynch).
> o Removed CheckStyle false positives for NewlineAtEndOfFile and whitespace 
> following '*' at end of line in javadoc.
> o Moved Clock interface to package org.apache.logging.log4j.core.helpers.
> o LOG4J2-225:  Documentation updates to clarify use and impact of location in 
> pattern layouts.
>
>
> Apache Log4j 2.0-beta6 requires a minimum of Java 6 to build and run. Basic 
> compatibility with
> Log4j 1.x is provided through the log4j-1.2-api component, however it does 
> not implement some of the
> very implementation specific classes and methods. The package names and Maven 
> groupId have been changed to
> org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
>
> For complete information on Apache Log4j 2, including instructions on how to 
> submit bug reports,
> patches, or suggestions for improvement, see the Apache Apache Log4j 2 
> website:
>
> http://logging.apache.org/log4j/2.x/



-- 
http://www.grobmeier.de
https://www.timeandbill.de

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

Reply via email to