Log4j 2.11.0 moves code from log4j-core to several new Maven modules. Dependencies to other jars that used to be optional in log4j-core are now required in the new modules. The code in these modules have been repackaged.
These changes do not affect your configuration files.
The new modules are:
Group ID: org.apache.logging.log4j
Artifact ID: log4j-cvs
Old package: org.apache.logging.log4j.core.layout
New package: org.apache.logging.log4j.csv.layout
Group ID: org.apache.logging.log4j
Artifact ID: log4j-jdbc
Old package: org.apache.logging.log4j.core.appender.db.jdbc
New package: org.apache.logging.log4j.jdbc.appender
Group ID: org.apache.logging.log4j
Artifact ID: log4j-jeromq
Old package: org.apache.logging.log4j.core.appender.mom.jeromq
New package: org.apache.logging.log4j.jeromq.appender
Group ID: org.apache.logging.log4j
Artifact ID: log4j-jms
Old package 1: org.apache.logging.log4j.core.appender.mom
New package 1: org.apache.logging.log4j.jms.appender
Group ID: org.apache.logging.log4j
Artifact ID: log4j-jpa
Old package 1: org.apache.logging.log4j.core.appender.db.jpa
New package 1: org.apache.logging.log4j.jpa.appender
Old package 2: org.apache.logging.log4j.core.appender.db.jpa.converter
New package 2: org.apache.logging.log4j.jpa.converter
Group ID: org.apache.logging.log4j
Artifact ID: log4j-kafka
Old package: org.apache.logging.log4j.core.appender.mom.kafka
New package: org.apache.logging.log4j.kafka.appender
Group ID: org.apache.logging.log4j
Artifact ID: log4j-mongodb2
Old package: org.apache.logging.log4j.mongodb
New package: org.apache.logging.log4j.mongodb2
Group ID: org.apache.logging.log4j
Artifact ID: log4j-mongodb3
Old package: org.apache.logging.log4j.mongodb
New package: org.apache.logging.log4j.mongodb3
Group ID: org.apache.logging.log4j
Artifact ID: log4j-smtp
Old package: org.apache.logging.log4j.core.appender
New package: org.apache.logging.log4j.smtp.appender
The Apache Log4j 2 team is pleased to announce the Log4j 2.10.0 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 other modern features such as support for Markers, lambda expressions for lazy logging, property substitution using Lookups, multiple patterns on a PatternLayout and asynchronous Loggers. Another notable Log4j 2 feature is the ability to be “garbage-free” (avoid allocating temporary objects) while logging. In addition, Log4j 2 will not lose events while reconfiguring.
This release contains new features, bugfixes and minor enhancements. Some of the new features include support for the Java 9 module system, support for the new SLF4j 1.8 binding mechanism, simplification of the Log4j property naming scheme, and native support of Jetty's logger. Log4j API is now a fully compliant module while the other Log4j jars are named automatic modules.
As of Log4j 2.9.0, the Log4j API was modified to use java.util.ServiceLoader to locate Log4j implementations, although the former binding mechanism is still supported. The Log4j API jar is now a multi-release jar to provide implementations of Java 9 specific classes. Multi-release jars are not supported by the OSGi specification so OSGi modules will not be able to take advantage of these implementations but will not lose functionality as they will fall back to the implementations used in Java 7 and 8. More details on the new features and fixes are itemized below. Note that some tools are not compatible with multi-release jars and may fail trying to process class files in the META-INF/versions/9 folder. Those errors should be reported to the tool vendor.
Note that subsequent to the 2.9.0 release, for security reasons, SerializedLayout is deprecated and no longer used as default in the Socket and JMS appenders. SerializedLayout can still be used as before, but has to be specified explicitly. To retain old behaviour, you have to change configuration like:
<Appenders> <Socket name="socket" host="localhost" port="9500"/> </Appenders>
into:
<Appenders>
<Socket name="socket" host="localhost" port="9500">
<SerializedLayout/>
</Socket>
</Appenders>
We do, however, discourage the use of SerializedLayout and recommend JsonLayout as a replacement:
<Appenders>
<Socket name="socket" host="localhost" port="9500">
<JsonLayout properties="true"/>
</Socket>
</Appenders>
Note that subsequent to the 2.9.0 release, for security reasons, Log4j does not process DTD in XML files. If you used DTD for including snippets, you have to use XInclude or Composite Configuration instead.
The Log4j 2.10.0 API, as well as many core components, maintains binary compatibility with previous releases.
Changes in this version include:
log4j.skipJansi to false). To avoid causing problems for web applications, Log4j will no longer automatically try to load Jansi without explicit configuration. Thanks to Andy Gumbrecht.Apache Log4j 2.10.0 requires a minimum of Java 7 to build and run. Log4j 2.3 was the last release that supported Java 6.
Basic compatibility with Log4j 1.x is provided through the log4j-1.2-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: