From general-return-1957-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sun Aug 5 18:11:45 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 73B0FD355 for ; Sun, 5 Aug 2012 18:11:45 +0000 (UTC) Received: (qmail 86347 invoked by uid 500); 5 Aug 2012 18:11:44 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 86176 invoked by uid 500); 5 Aug 2012 18:11:43 -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 86147 invoked by uid 99); 5 Aug 2012 18:11:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Aug 2012 18:11:43 +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 (nike.apache.org: domain of ralph.goers@dslextreme.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Aug 2012 18:11:33 +0000 Received: by obc16 with SMTP id 16so1228833obc.34 for ; Sun, 05 Aug 2012 11:11:12 -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=e7o/SNdmtbXRqpHaINOUM3xTZWloyGhXs6jOz8Ygoso=; b=Z5DqtAlVumu0EbtqY54vqXXHchiBdalHxpffB0V6/HKIRqLRoMJFLXBnVug7A1orBK qBQzaoqsI3xPTPGasRTl7umz1IWtyrMwkq9bj31gOhD+cU2aePd5DahCPoQBVJIOShw1 dFERA04XQ186ISGruadSgHMNL5VV8e5vWZqYZK1hSUe6Gzh+Rip7/ROAHy0jyBf7oOmj KFBoJPFarZvY7lzIW7uZYXTXySXFzLfr1h4nSU0Ikj5MS7L68BDJA+VmM7nPAZ//Hno7 8cmBQW4prmaPCSEXWDw/jixbk6/SiYU78SMQAYRRjx2eM/dB09FMMzLr1jHT3UUnWWRO 9puA== Received: by 10.182.167.41 with SMTP id zl9mr15385400obb.43.1344190272582; Sun, 05 Aug 2012 11:11:12 -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 aa6sm11867879oec.0.2012.08.05.11.11.10 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 05 Aug 2012 11:11:11 -0700 (PDT) From: Ralph Goers Content-Type: multipart/alternative; boundary="Apple-Mail=_9325F93F-D061-4A7E-A902-E43BAF6AE4E0" Subject: [ANNOUNCEMENT] Apache Logging log4j 2.0-alpha1 released Date: Sun, 5 Aug 2012 11:11:18 -0700 Message-Id: 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: ALoCoQlrJvewzJ4mdZRXA9zg+PBo4SBAipVPfSe4DtmU+lbD7EtuCOgBHSvaR4UZJVtMnMKw8lBf --Apple-Mail=_9325F93F-D061-4A7E-A902-E43BAF6AE4E0 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-alpha1 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 first release of Log4j 2 and is being made available to get = feedback from the community. Some of the features and improvements in Log4j 2 are: * API Separation - The API for Log4j is separate from the = implementation. It is now clear to application developers what classes and methods they can use with compatibility = being assured, while also=20 allowing improvements to be made to the implementation. * Designed for Audit Logging - Unlike Log4j 1.x and Logback, Log4j 2 = will not lose events during=20 reconfiguration. Log4j 2 also supports Messages, which easily allow = audit events to be flow through the framework. * Improved Performance - Faster performance than Log4j 1.x in critical = areas and similar performance=20 to Logback in most circumstances.=20 * Support for multiple APIs - While the Log4j 2 API will provide the = best performance, support for SLF4J=20 and Commons Logging APIs are provided. * Automatic Reloading of Configurations - Like Logback, Log4j 2 supports = filtering based on context data, markers, regular expressions and other components in the Log event and = can be specified to apply to all events before being passed to Loggers or as they pass through = Appenders. In addition, filters can also be associated with Loggers, Unlike Logback, a common Filter = class can be used in any=20 of these circumstances. Log4j 2 currently supports configuration via XML = or JSON. * Plugin Architecture - All configurable components are defined as Log4j = plugins. As such, no=20 Log4j code must be changed to create a new Appender, Layout, Pattern = Converter, etc.=20 Log4j will automatically recognize properly defined plugins and use them = when they are=20 referenced in the configuration. * Property Support - Properties can be referenced in the configuration = and either be directly=20 replace or passed to the underlying component where they can be = dynamically resolved.=20 Properties can come from values defined in the configuration file, = system properties,=20 environment variables, the ThreadContext Map, and data present in the = event. Users can further customize the property providers by adding their own Lookup = Plugin For more information see the Log4j 2 web site at = http://logging.apache.org/log4j/2.x/index.html Apache log4j 2.0 requires JDK 5 or later. --Apple-Mail=_9325F93F-D061-4A7E-A902-E43BAF6AE4E0 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-alpha1 = 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 = first release of Log4j 2 and is being made available to get feedback = from the community.

Some of the features and = improvements in Log4j 2 are:

* API Separation - = The API for Log4j is separate from the implementation. It is now clear = to application
developers what classes and methods they can = use with compatibility being assured, while = also 
allowing improvements to be made to the = implementation.

* Designed for Audit Logging - = Unlike Log4j 1.x and Logback, Log4j 2 will not lose events = during 
reconfiguration. Log4j 2 also supports Messages, = which easily allow audit events to be flow through
the = framework.

* Improved Performance - Faster = performance than Log4j 1.x in critical areas and similar = performance 
to Logback in most = circumstances. 

* Support for multiple = APIs - While the Log4j 2 API will provide the best performance, support = for SLF4J 
and Commons Logging APIs are = provided.

* Automatic Reloading of = Configurations - Like Logback, Log4j 2 supports filtering based on = context data,
markers, regular expressions and other = components in the Log event and can be specified to apply
to = all events before being passed to Loggers or as they pass through = Appenders. In addition, filters
can also be associated with = Loggers, Unlike Logback, a common Filter class can be used in = any 
of these circumstances. Log4j 2 currently supports = configuration via XML or JSON.

* Plugin = Architecture - All configurable = components are defined as Log4j plugins. As such, = no 
Log4j code must be = changed to create a new Appender, Layout, Pattern Converter, = etc. 

* Property Support - Properties can be referenced in the configuration = and either be directly 
replace or passed to the underlying component where = they can be dynamically resolved. 
Properties can come from values defined in the = configuration file, system properties, 
environment variables, the ThreadContext Map, and = data present in the event. Users can
further customize the property providers by adding = their own Lookup http://logging.apa= che.org/log4j/2.x/index.html

Apache log4j 2.0 requires = JDK 5 or later.
= --Apple-Mail=_9325F93F-D061-4A7E-A902-E43BAF6AE4E0--