Ceki Gulcu: log4j version 1.0 released

Download the authoritative guide: Data Center Guide: Optimizing Your Data Center Strategy

Download the authoritative guide: Cloud Computing: Using the Cloud for Competitive Advantage

I am pleased to announce log4j version 1.0, the 20th public release of log4j and the first under the Apache banner.
Date: Tue, 09 Jan 2001 04:24:41 +0100
From: Ceki Gulcu ceki@apache.org
To: announce@apache.org
Subject: log4j version 1.0
Greetings everyone,
I am pleased to announce log4j version 1.0, the 20th public release of
log4j and the first under the Apache banner.
For those unfamiliar with the name, log4j is a popular logging package
written in Java. log4j allows you to log to a file, a java.io.Writer,
a remote server, NT Event Log or a syslog daemon.  The package is
designed so that log statements can remain in shipped code without
incurring a high performance cost. One distinctive feature of log4j is
the notion of hierarchical categories. Using categories, it is
possible to select (at runtime) which log statements are output at
arbitrary granularity. Users can choose to implement their own log
formats and output strategies.
This release brings a number of new features along with bug fixes.
The most important change is that log4j is now part of the Jakarta
project of the Apache Software Foundation. Consequently, the package
hierarchy now starts at org.apache.log4j instead of org.log4j.
I have also taken advantage of this release to drop the EMERG priority
and replace it with FATAL which is more widely understood.
This version fixes all known bugs. It also adds a number of features
such as the SMTPAppender, HTMLLayout, JMSAppender and ObjectRenderers.
The PropertyConfigurator has been enhanced to support variable
substitution for all option values, support for specifying the
category factory and object renderers. Just as importantly, both the
DOMConfigurator and the PropertyConfigurator can be used to configure
any given hierarchy not just the default one.
The HISTORY file reads:
    [*] Changes that are 100% compatible with existing client code.
   [**] Changes that requiring little or no modification to existing
        client code.
  [***] Changes requiring important modifications to existing client code.

This article was originally published on Jan 9, 2001
Page 1 of 2

Thanks for your registration, follow us on our social networks to keep up-to-date