From general-return-1971-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sat Sep 22 05:39:46 2012 Return-Path: X-Original-To: apmail-logging-general-archive@www.apache.org Delivered-To: apmail-logging-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57450D768 for ; Sat, 22 Sep 2012 05:39:46 +0000 (UTC) Received: (qmail 29946 invoked by uid 500); 22 Sep 2012 05:39:43 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 29527 invoked by uid 500); 22 Sep 2012 05:39:38 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 29487 invoked by uid 99); 22 Sep 2012 05:39:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 05:39:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ralph.goers@dslextreme.com designates 209.85.219.47 as permitted sender) Received: from [209.85.219.47] (HELO mail-oa0-f47.google.com) (209.85.219.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 05:39:28 +0000 Received: by oagn9 with SMTP id n9so4375020oag.34 for ; Fri, 21 Sep 2012 22:39:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:subject:date:message-id:to:mime-version:x-mailer :x-gm-message-state; bh=CH7d1pSP/plRezE0nSUG4wIX5vyXwaO6uHG3f8NYWyQ=; b=m+BLUSamfqlEwISIRZxJNyxuIXguHd3gb75N0Q32fB20Jb+grOReG0/asak7nmIMQt lRFjtaUkH/6JzmCOX8V3KyEUEHKkLzdPR4Megoh6AHvEERrzM8KJrzRSwq1P0Z5aYDSA LN4o4h7qaUxVaJveIhGzzrcnY8ceEw18EBtgxh6JCDRrwHN4HtJf8aUIyuKi++fEnvB/ SjIKENvZJ28SsY7tj9o1ys24li+KHqwpzXanM54AnaBybcC2nSgs0x8qC9FS5KcLhDjG jmrHYFjCZpCreNNeazzPrf7elNXJxGE8uZkkR2LVGgmUXywhLocm3JEFwnuTVpKp3+v4 Vfmg== Received: by 10.60.170.229 with SMTP id ap5mr5441480oec.101.1348292346288; Fri, 21 Sep 2012 22:39:06 -0700 (PDT) Received: from [192.168.1.92] (99-180-69-21.lightspeed.irvnca.sbcglobal.net. [99.180.69.21]) by mx.google.com with ESMTPS id ac10sm9916123obc.7.2012.09.21.22.39.04 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Sep 2012 22:39:05 -0700 (PDT) From: Ralph Goers Content-Type: multipart/alternative; boundary="Apple-Mail=_BF58CF17-4386-4E2B-B8AE-7B15A94E93E1" Subject: [ANNOUNCEMENT] Apache Logging log4j 2.0-beta1 released Date: Fri, 21 Sep 2012 22:39:03 -0700 Message-Id: <22EBA3FF-6477-4159-8C33-6415B201990B@dslextreme.com> To: Log4J Developers List , Log4J Users List , Logging General Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) X-Gm-Message-State: ALoCoQmRkPTJl3/4DH/WYNwDEX78p9+lfgmqEYjYv2BzcRbVMu+X9IT/ks08EMojK4g25aQfjevR X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_BF58CF17-4386-4E2B-B8AE-7B15A94E93E1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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=20 Log4j that provides significant improvements over its predecessor, Log4j = 1.x, and provides=20 many of the improvements available in Logback while fixing some inherent = problems in Logback's=20 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.=20 Fixed Bugs: o LOG4J-81: PatternLayout was not honoring format modifiers.=20 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.=20 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.=20 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.=20 o LOG4J2-78: LogFactoryImpl.setAttribute in the Commons Logging bridge = got a NullPointerException when passed a null value. It will now remove the attribute.=20 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.=20 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.=20 o LOG4J2-74: Logger.error(Marker, Message, Throwable) was internally = using Level.TRACE.=20 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.=20 o LOG4J2-72: NullPointerException in RollingFileManager when = filePattern does not cause the file to be compressed.=20 o LOG4J2-71: FileRenameAction did not create the parent directories of = the archive files causing the rollover to fail.=20 Changes: o Update the versions of SLF4J and Logback.=20 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/ --Apple-Mail=_BF58CF17-4386-4E2B-B8AE-7B15A94E93E1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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 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:


= --Apple-Mail=_BF58CF17-4386-4E2B-B8AE-7B15A94E93E1--