- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
Ceki Gulcu: log4j version 1.0 released
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 firstname.lastname@example.org To: email@example.com 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.