You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2012/09/22 07:39:03 UTC
[ANNOUNCEMENT] Apache Logging log4j 2.0-beta1 released
The Apache Logging team is pleased to announce the Apache log4j 2.0-beta1 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 third 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:
New features:
o Added AsynchAppender.
Fixed Bugs:
o LOG4J-81: PatternLayout was not honoring format modifiers.
o Created web module to allow web applications to include the Log4j context listener in WEB-INF/lib even if
Log4j is in the container's class path. Allow locating the LoggerContext to include the ClassLoader. Updated
the Loader utility to always choose the child ClassLoader. Verified in Jboss 5 and Tomcat.
o LOG4J2-82: MarkerFilter called MarkerManager.getMarker causing the Marker to be created during the processing of the
configuration. This prevents the application from creating the Marker with any parents. MarkerWrapper in
SLF4J-impl was getting a ClassCastException in instanceOf because the Marker isn't a MarkerWrapper.
o LOG4J2-80: Allow Log4j 2 to be used as the implementation with SLF4J and SLF4J's jcl-over-slf4j by adding filtering
to the log method in SLF4JLogger. Thanks to Oliver Lamy.
o LOG4J2-78: LogFactoryImpl.setAttribute in the Commons Logging bridge got a NullPointerException when passed a null value.
It will now remove the attribute.
o LOG4J2-77: RoutingAppender was calling the stop method for each of its referenced Appenders and was calling
the stop method of the default Appender a second time. It will now only call the stop method of
Appenders it creates.
o LOG4J2-76: RewriteAppender was calling the stop method of the referenced appender causing the referenced appender's
manager to have its use count decremented too many times.
o LOG4J2-74: Logger.error(Marker, Message, Throwable) was internally using Level.TRACE.
o LOG4J2-75: Enhanced Log4jContextListener to accept a configuration file location. Modified FileConfigurationMonitor
to monitor files configured that way. Fixed other reconfiguration related bugs. Tested in JBoss and
Tomcat.
o LOG4J2-72: NullPointerException in RollingFileManager when filePattern does not cause the file to be compressed.
o LOG4J2-71: FileRenameAction did not create the parent directories of the archive files causing the rollover to fail.
Changes:
o Update the versions of SLF4J and Logback.
Apache Log4j 2.0-beta1 requires a minimum of Java 5 to build and run. Basic compatibility with
Log4j 1.x is provided through the log4j12-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/
Re: [ANNOUNCEMENT] Apache Logging log4j 2.0-beta1 released
Posted by Christian Grobmeier <gr...@gmail.com>.
And forwarded it to: announce@apache.org
which is also important imho
On Mon, Sep 24, 2012 at 7:41 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> Thanks!
>
> I have added it to the blog:
> https://blogs.apache.org/logging/entry/apache_log4j_2_0_beta1
>
> Cheers!
>
> On Sat, Sep 22, 2012 at 7:39 AM, Ralph Goers <ra...@dslextreme.com> wrote:
>> The Apache Logging team is pleased to announce the Apache log4j 2.0-beta1
>> 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 third 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:
>>
>> New features:
>> o Added AsynchAppender.
>>
>> Fixed Bugs:
>> o LOG4J-81: PatternLayout was not honoring format modifiers.
>> o Created web module to allow web applications to include the Log4j context
>> listener in WEB-INF/lib even if
>> Log4j is in the container's class path. Allow locating the
>> LoggerContext to include the ClassLoader. Updated
>> the Loader utility to always choose the child ClassLoader. Verified
>> in Jboss 5 and Tomcat.
>> o LOG4J2-82: MarkerFilter called MarkerManager.getMarker causing the Marker
>> to be created during the processing of the
>> configuration. This prevents the application from creating the
>> Marker with any parents. MarkerWrapper in
>> SLF4J-impl was getting a ClassCastException in instanceOf because
>> the Marker isn't a MarkerWrapper.
>> o LOG4J2-80: Allow Log4j 2 to be used as the implementation with SLF4J and
>> SLF4J's jcl-over-slf4j by adding filtering
>> to the log method in SLF4JLogger. Thanks to Oliver Lamy.
>> o LOG4J2-78: LogFactoryImpl.setAttribute in the Commons Logging bridge got
>> a NullPointerException when passed a null value.
>> It will now remove the attribute.
>> o LOG4J2-77: RoutingAppender was calling the stop method for each of its
>> referenced Appenders and was calling
>> the stop method of the default Appender a second time. It will now
>> only call the stop method of
>> Appenders it creates.
>> o LOG4J2-76: RewriteAppender was calling the stop method of the referenced
>> appender causing the referenced appender's
>> manager to have its use count decremented too many times.
>> o LOG4J2-74: Logger.error(Marker, Message, Throwable) was internally using
>> Level.TRACE.
>> o LOG4J2-75: Enhanced Log4jContextListener to accept a configuration file
>> location. Modified FileConfigurationMonitor
>> to monitor files configured that way. Fixed other reconfiguration
>> related bugs. Tested in JBoss and
>> Tomcat.
>> o LOG4J2-72: NullPointerException in RollingFileManager when filePattern
>> does not cause the file to be compressed.
>> o LOG4J2-71: FileRenameAction did not create the parent directories of the
>> archive files causing the rollover to fail.
>>
>> Changes:
>> o Update the versions of SLF4J and Logback.
>>
>> Apache Log4j 2.0-beta1 requires a minimum of Java 5 to build and run. Basic
>> compatibility with
>> Log4j 1.x is provided through the log4j12-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
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [ANNOUNCEMENT] Apache Logging log4j 2.0-beta1 released
Posted by Christian Grobmeier <gr...@gmail.com>.
Thanks!
I have added it to the blog:
https://blogs.apache.org/logging/entry/apache_log4j_2_0_beta1
Cheers!
On Sat, Sep 22, 2012 at 7:39 AM, Ralph Goers <ra...@dslextreme.com> wrote:
> The Apache Logging team is pleased to announce the Apache log4j 2.0-beta1
> 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 third 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:
>
> New features:
> o Added AsynchAppender.
>
> Fixed Bugs:
> o LOG4J-81: PatternLayout was not honoring format modifiers.
> o Created web module to allow web applications to include the Log4j context
> listener in WEB-INF/lib even if
> Log4j is in the container's class path. Allow locating the
> LoggerContext to include the ClassLoader. Updated
> the Loader utility to always choose the child ClassLoader. Verified
> in Jboss 5 and Tomcat.
> o LOG4J2-82: MarkerFilter called MarkerManager.getMarker causing the Marker
> to be created during the processing of the
> configuration. This prevents the application from creating the
> Marker with any parents. MarkerWrapper in
> SLF4J-impl was getting a ClassCastException in instanceOf because
> the Marker isn't a MarkerWrapper.
> o LOG4J2-80: Allow Log4j 2 to be used as the implementation with SLF4J and
> SLF4J's jcl-over-slf4j by adding filtering
> to the log method in SLF4JLogger. Thanks to Oliver Lamy.
> o LOG4J2-78: LogFactoryImpl.setAttribute in the Commons Logging bridge got
> a NullPointerException when passed a null value.
> It will now remove the attribute.
> o LOG4J2-77: RoutingAppender was calling the stop method for each of its
> referenced Appenders and was calling
> the stop method of the default Appender a second time. It will now
> only call the stop method of
> Appenders it creates.
> o LOG4J2-76: RewriteAppender was calling the stop method of the referenced
> appender causing the referenced appender's
> manager to have its use count decremented too many times.
> o LOG4J2-74: Logger.error(Marker, Message, Throwable) was internally using
> Level.TRACE.
> o LOG4J2-75: Enhanced Log4jContextListener to accept a configuration file
> location. Modified FileConfigurationMonitor
> to monitor files configured that way. Fixed other reconfiguration
> related bugs. Tested in JBoss and
> Tomcat.
> o LOG4J2-72: NullPointerException in RollingFileManager when filePattern
> does not cause the file to be compressed.
> o LOG4J2-71: FileRenameAction did not create the parent directories of the
> archive files causing the rollover to fail.
>
> Changes:
> o Update the versions of SLF4J and Logback.
>
> Apache Log4j 2.0-beta1 requires a minimum of Java 5 to build and run. Basic
> compatibility with
> Log4j 1.x is provided through the log4j12-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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[ANNOUNCEMENT] Apache Logging log4j 2.0-beta1 released
Posted by Christian Grobmeier <gr...@apache.org>.
The Apache Logging team is pleased to announce the Apache log4j
2.0-beta1 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 third 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:
New features:
o Added AsynchAppender.
Fixed Bugs:
o LOG4J-81: PatternLayout was not honoring format modifiers.
o Created web module to allow web applications to include the Log4j
context listener in WEB-INF/lib even if
Log4j is in the container's class path. Allow locating the
LoggerContext to include the ClassLoader. Updated
the Loader utility to always choose the child ClassLoader.
Verified in Jboss 5 and Tomcat.
o LOG4J2-82: MarkerFilter called MarkerManager.getMarker causing the
Marker to be created during the processing of the
configuration. This prevents the application from creating the
Marker with any parents. MarkerWrapper in
SLF4J-impl was getting a ClassCastException in instanceOf
because the Marker isn't a MarkerWrapper.
o LOG4J2-80: Allow Log4j 2 to be used as the implementation with
SLF4J and SLF4J's jcl-over-slf4j by adding filtering
to the log method in SLF4JLogger. Thanks to Oliver Lamy.
o LOG4J2-78: LogFactoryImpl.setAttribute in the Commons Logging
bridge got a NullPointerException when passed a null value.
It will now remove the attribute.
o LOG4J2-77: RoutingAppender was calling the stop method for each of
its referenced Appenders and was calling
the stop method of the default Appender a second time. It will
now only call the stop method of
Appenders it creates.
o LOG4J2-76: RewriteAppender was calling the stop method of the
referenced appender causing the referenced appender's
manager to have its use count decremented too many times.
o LOG4J2-74: Logger.error(Marker, Message, Throwable) was internally
using Level.TRACE.
o LOG4J2-75: Enhanced Log4jContextListener to accept a configuration
file location. Modified FileConfigurationMonitor
to monitor files configured that way. Fixed other
reconfiguration related bugs. Tested in JBoss and
Tomcat.
o LOG4J2-72: NullPointerException in RollingFileManager when
filePattern does not cause the file to be compressed.
o LOG4J2-71: FileRenameAction did not create the parent directories
of the archive files causing the rollover to fail.
Changes:
o Update the versions of SLF4J and Logback.
Apache Log4j 2.0-beta1 requires a minimum of Java 5 to build and run.
Basic compatibility with
Log4j 1.x is provided through the log4j12-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/