Apache Logging Services
Apache Logging log4j 2.0-alpha1 released
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 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. Log4j will automatically recognize properly defined plugins and use them when they are referenced in the configuration.
- 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 Plugin
For more information see the Log4j 2 web site
Apache log4j 2.0 requires JDK 5 or later.
The Apache Logging team upgraded all Logging websites to the Apache CMS. This was a huge effort for the whole team. And we were very glad we got so much help from the Apache Infrastructure and the Apache Maven team (esp. Hervé Boutemy) - thank you very much to all who spent their time.
Now we have a great new landing page, based on Twig and Twitters Bootstrap. Updates to the files are turned into plain HTML by the CMS. You can look at these files here. The Logging project does maintain several subsites. These have been included as so called "extpaths". Now it is possible for us to build our subsites with maven and copy the result to a specific svn tree. From there it is taken by the CMS and published. You can look at the subsites code here.
Most subsites are still in the "plain maven look and feel". Except the webpages for Apache log4j 2, which does already wear the layout of the fantastic Apache Maven Fluido Skin.
The Apache CMS is a pretty fabulous tool. It is extremely flexible in that you can use what it offers out of the box, you can customize it to use a different templating mechanism as we did, or you can have the system run Maven to build your site. For us, using the CMS for the main set of web pages provides us a way to quickly maintain the main part of the site while each of our subprojects is still free to generate all the build documentation Java developers have become accustomed to.
Again, we really want to that the Apache Infrastructure team for creating this tool and providing support to us along the way.
log4j 2 is on the main trunk
After 2 years of experimental development the Apache Logging project has moved the log4j 2.0 code to the main trunk of log4j. You can find the code at
Log4j 2.0 supports Java 5.0 and has many interesting features including:
- Support for using the SLF4J or Commons Logging APIs
- Configuration via JSON (as well as XML)
- Automatic reloading of configurations without losing logging events
- Plugin architecture that allows new components to easily be added
- Allows variables from System Properties, MDC, Log event data, and more to be accessed in the configuration
Your help would be greatly appreciated! Please provide feedback, suggestions and questions to firstname.lastname@example.org.
Patches, enhancement requests and bugs can be reported to: https://issues.apache.org/jira/browse/LOG4J2
A website is prepared but has not been deployed to logging.apache.org yet. Ralph Goers, who initiated the work on Log4j2, has uploaded a preview at
Your Logging team
Apache log4php 2.2.1 released
The Apache log4php team is pleased to announce the release of Apache
This is a maintenance release which fixes several important bugs and
features yet another update to the web site design.
The full changelog can be found at:
The release is available from:
Thanks to everyone who participated in the making of this release.
The Apache log4php team
Apache log4php 2.2.0 released
The Apache log4php team is pleased to announce the release of Apache log4php 2.2.0.
Significant changes in this release include:
- a full rewrite of the configuration logic which greatly improves error reporting
- inline configuration using PHP arrays
- a new web site with better documentation and more examples
- a new layout: serialized
Release notes, including the full change, log can be found here: http://logging.apache.org/log4php/changelog.html
The release is available from: http://logging.apache.org/log4php/download.html
The site has just been updated so it may take a little while to sync.
Thanks to everyone who participated in the making of this release.Best regards,
The Apache log4php team