"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "RELEASE-NOTES.md" between
apache-log4j-2.11.1-src.tar.gz and apache-log4j-2.11.2-src.tar.gz

About: Apache Log4j 2 is a logging library for Java. Source distribution (Java).

RELEASE-NOTES.md  (apache-log4j-2.11.1-src):RELEASE-NOTES.md  (apache-log4j-2.11.2-src)
skipping to change at line 17 skipping to change at line 17
the License. You may obtain a copy of the License at the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0 http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and See the License for the specific language governing permissions and
limitations under the License. limitations under the License.
--> -->
# Apache Log4j 2.11.1 Release Notes # Apache Log4j 2.11.2 Release Notes
The Apache Log4j 2 team is pleased to announce the Log4j 2.11.1 release! The Apache Log4j 2 team is pleased to announce the Log4j 2.11.2 release!
Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade 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 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 l azy logging, many other modern features such as support for Markers, lambda expressions for l azy logging,
property substitution using Lookups, multiple patterns on a PatternLayout and as ynchronous property substitution using Lookups, multiple patterns on a PatternLayout and as ynchronous
Loggers. Another notable Log4j 2 feature is the ability to be "garbage-free" (av oid allocating Loggers. Another notable Log4j 2 feature is the ability to be "garbage-free" (av oid allocating
temporary objects) while logging. In addition, Log4j 2 will not lose events whil e reconfiguring. temporary objects) while logging. In addition, Log4j 2 will not lose events whil e reconfiguring.
This release contains new features, bugfixes and minor enhancements. The artifacts may be downloaded from https://logging.apache.org/log4j/2.x/downlo
ad.html.
This release contains bugfixes and minor enhancements.
Due to a break in compatibility in the SLF4J binding, Log4j now ships with two v ersions of the SLF4J to Log4j adapters. Due to a break in compatibility in the SLF4J binding, Log4j now ships with two v ersions of the SLF4J to Log4j adapters.
log4j-slf4j-impl should be used with SLF4J 1.7.x and earlier and log4j-slf4j18-i mpl should be used with SLF4J 1.8.x and log4j-slf4j-impl should be used with SLF4J 1.7.x and earlier and log4j-slf4j18-i mpl should be used with SLF4J 1.8.x and
later. later.
As of Log4j 2.9.0, the Log4j API was modified to use java.util.ServiceLoader to locate Log4j implementations, 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 n ow a multi-release jar although the former binding mechanism is still supported. The Log4j API jar is n ow a multi-release jar
to provide implementations of Java 9 specific classes. Multi-release jars are no t supported by to provide implementations of Java 9 specific classes. Multi-release jars are no t supported by
the OSGi specification so OSGi modules will not be able to take advantage of the se implementations the OSGi specification so OSGi modules will not be able to take advantage of the se implementations
but will not lose functionality as they will fall back to the implementations us but will not lose functionality as they will fall back to the implementations us
ed in Java 7 and 8. ed in Java 7 and 8. Applications
More details on the new features and fixes are itemized below. Note that some to using Spring Boot must add the Multi-Release header to the jar manifest or the J
ols are not compatible ava 9+ classes will be
ignored.
More details on the fixes are itemized below. Note that some tools are not comp
atible
with multi-release jars and may fail trying to process class files in the META-I NF/versions/9 folder. with multi-release jars and may fail trying to process class files in the META-I NF/versions/9 folder.
Those errors should be reported to the tool vendor. Those errors should be reported to the tool vendor.
Note that subsequent to the 2.9.0 release, for security reasons, SerializedLayou Note that subsequent to the 2.9.0 release, for security reasons, Log4j does not
t is deprecated and no process DTD in XML files.
If you used DTD for including snippets, you have to use XInclude or Composite Co
nfiguration instead.
Also 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 sti ll be used as before, longer used as default in the Socket and JMS appenders. SerializedLayout can sti ll be used as before,
but has to be specified explicitly. To retain old behaviour, you have to change configuration like: but has to be specified explicitly. To retain old behaviour, you have to change configuration like:
<Appenders> <Appenders>
<Socket name="socket" host="localhost" port="9500"/> <Socket name="socket" host="localhost" port="9500"/>
</Appenders> </Appenders>
into: into:
<Appenders> <Appenders>
skipping to change at line 67 skipping to change at line 75
</Appenders> </Appenders>
We do, however, discourage the use of SerializedLayout and recommend JsonLayout as a replacement: We do, however, discourage the use of SerializedLayout and recommend JsonLayout as a replacement:
<Appenders> <Appenders>
<Socket name="socket" host="localhost" port="9500"> <Socket name="socket" host="localhost" port="9500">
<JsonLayout properties="true"/> <JsonLayout properties="true"/>
</Socket> </Socket>
</Appenders> </Appenders>
Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they no Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they no
longer have the "timeMillis" attribute and instead have an "Instant" element wit longer have the "timeMillis" attribute
h "epochSecond" and "nanoOfSecond" attributes. and instead have an "Instant" element with "epochSecond" and "nanoOfSecond" attr
ibutes.
Note that subsequent to the 2.9.0 release, for security reasons, Log4j does not The Log4j 2.11.2 API, as well as many core components, maintains binary compatib
process DTD in XML files. ility with previous releases.
If you used DTD for including snippets, you have to use XInclude or Composite Co
nfiguration instead.
The Log4j 2.11.1 API, as well as many core components, maintains binary compatib ## GA Release 2.11.2
ility with previous releases.
## GA Release 2.11.1
Changes in this version include: Changes in this version include:
### New Features
* [LOG4J2-2496](https://issues.apache.org/jira/browse/LOG4J2-2496):
JDBC Appender should reconnect to the database when a connection goes stale.
* [LOG4J2-2505](https://issues.apache.org/jira/browse/LOG4J2-2505):
Let JDBC PoolingDriverConnectionSource with Apache Commons DBCP configure a Pool
ableConnectionFactory.
* [LOG4J2-2509](https://issues.apache.org/jira/browse/LOG4J2-2509):
Allow a JDBC Appender to truncate strings to match a table's metadata column len
gth limit.
* [LOG4J2-1246](https://issues.apache.org/jira/browse/LOG4J2-1246):
PatternLayout %date conversion pattern should render time zone designator for IS
O-ISO8601.
### Fixed Bugs ### Fixed Bugs
* [LOG4J2-2389](https://issues.apache.org/jira/browse/LOG4J2-2389): * [LOG4J2-2500](https://issues.apache.org/jira/browse/LOG4J2-2500):
ThrowableProxy was saving and retrieving cache entries using different keys. Tha Document that Properties element must be the first configuration element.
nks to Liu Wen. * [LOG4J2-2543](https://issues.apache.org/jira/browse/LOG4J2-2543):
* [LOG4J2-2316](https://issues.apache.org/jira/browse/LOG4J2-2316): Add Log4j-to-SLF4J to BOM pom.xml. Thanks to Dermot Hardy.
If root LoggerConfig does not have a Level return ERROR. * [LOG4J2-2061](https://issues.apache.org/jira/browse/LOG4J2-2061):
* [LOG4J2-2390](https://issues.apache.org/jira/browse/LOG4J2-2390): Use the file pattern as the FileManager "name" when no filename is present.
Fix broken links in log4j web documentation. Thanks to anton-balaniuc. * [LOG4J2-2009](https://issues.apache.org/jira/browse/LOG4J2-2009):
* [LOG4J2-2343](https://issues.apache.org/jira/browse/LOG4J2-2343): Expose LoggerContext.setConfiguration as a public method.
The OSGi Activator specified an incorrect version. Thanks to Raymond Augé. * [LOG4J2-2542](https://issues.apache.org/jira/browse/LOG4J2-2542):
* [LOG4J2-2305](https://issues.apache.org/jira/browse/LOG4J2-2305): CronTriggeringPolicy was not rolling properly, especially when used with the Siz
Make java.util.ServiceLoader properly work in OSGi by using the Service Loader M eBasedTriggeringPolicy.
ediator Specification. Thanks to Björn Kautler. * [LOG4J2-2266](https://issues.apache.org/jira/browse/LOG4J2-2266):
* [LOG4J2-2305](https://issues.apache.org/jira/browse/LOG4J2-2305): Load PropertySources from any accessible ClassLoader. Hide any exceptions that m
Split the SLF4J binding into 2 implementations - one for SLF4J 1.7.x and one for ay occur accessing a PropertySource.
SLF4J 1.8+. * [LOG4J2-1570](https://issues.apache.org/jira/browse/LOG4J2-1570):
* [LOG4J2-2268](https://issues.apache.org/jira/browse/LOG4J2-2268): Logging with a lambda expression with a method call that also logs would cause l
Improve plugin error message when elements are missing. Thanks to Tilman Hausher ogs within method call to reference line num and method name of the parent metho
r. d.
* [LOG4J2-2283](https://issues.apache.org/jira/browse/LOG4J2-2283): * [LOG4J2-2485](https://issues.apache.org/jira/browse/LOG4J2-2485):
ParserConfigurationException when using Log4j with oracle.xml.jaxp.JXDocumentBui SizeBasedTriggeringPolicy was not honored when using the DirectWriteRolloverStra
lderFactory. Thanks to Vishnu Priya Matha. tegy if the machine restarts. Thanks to Giovanni Matteo Fumarola.
* [LOG4J2-2300](https://issues.apache.org/jira/browse/LOG4J2-2300): * [LOG4J2-1906](https://issues.apache.org/jira/browse/LOG4J2-1906):
PoolingDriverConnectionSource does not take into account properties, user name, Direct write was creating files with the wrong date/time.
and password. * [LOG4J2-2453](https://issues.apache.org/jira/browse/LOG4J2-2453):
* [LOG4J2-2307](https://issues.apache.org/jira/browse/LOG4J2-2307): Add Log4j-slf4j18-impl dependency to bom pom. Thanks to theit.
MutableLogEvent and RingBufferLogEvent message mementos retain the original form * [LOG4J2-2515](https://issues.apache.org/jira/browse/LOG4J2-2515):
at string. Configuration documentation referenced incorrect method name. Thanks to MakarovS
* [LOG4J2-2032](https://issues.apache.org/jira/browse/LOG4J2-2032): .
Curly braces in parameters are not treated as placeholders. Thanks to Kostiantyn * [LOG4J2-2514](https://issues.apache.org/jira/browse/LOG4J2-2514):
Shchepanovskyi. Make Strings.toRootUpperCase a static method so it can be accessed. Thanks to sm
* [LOG4J2-2317](https://issues.apache.org/jira/browse/LOG4J2-2317): ilebrian0515.
MutableLogEvent.getNonNullImmutableMessage and Log4jLogEvent.makeMessageImmutabl * [LOG4J2-1571](https://issues.apache.org/jira/browse/LOG4J2-1571):
e retain format and parameters. Fixed Appenders section in Extending Log4j. Thanks to torbenmoeller.
* [LOG4J2-2318](https://issues.apache.org/jira/browse/LOG4J2-2318): * [LOG4J2-2397](https://issues.apache.org/jira/browse/LOG4J2-2397):
Messages are no longer mutated when the asynchronous queue is full. A warning is Predeployment of PersistenceUnit that using Log4j as session logger failed (#198
logged to the status logger instead. ). Thanks to EckelDong.
* [LOG4J2-2320](https://issues.apache.org/jira/browse/LOG4J2-2320): * [LOG4J2-2365](https://issues.apache.org/jira/browse/LOG4J2-2365):
Fix NPE in AbstractLogger when another exception is thrown, masking the root cau NameAbbreviator correctly abbreviates first fragments (#188). Thanks to Eugene Z
se. imichev.
* [LOG4J2-2321](https://issues.apache.org/jira/browse/LOG4J2-2321): * [LOG4J2-2201](https://issues.apache.org/jira/browse/LOG4J2-2201):
AsyncLogger uses the correct level when unspecified. This provides parity betwee Fix memory leak in ReusableParameterizedMessage.
n AsyncLogger and Logger. * [LOG4J2-2363](https://issues.apache.org/jira/browse/LOG4J2-2363):
* [LOG4J2-2322](https://issues.apache.org/jira/browse/LOG4J2-2322): ReusableObjectMessage parameter is properly passed to appenders (#203). Thanks t
Custom ContextSelector implementations which select an AsyncLoggerContext disabl o Brian Laub.
e LoggerConfig.includeLocation * [LOG4J2-2418](https://issues.apache.org/jira/browse/LOG4J2-2418):
by default for parity with AsyncLoggerContextSelector. NullPointerException when closing never used RollingRandomAccessFileAppender. Th
* [LOG4J2-2269](https://issues.apache.org/jira/browse/LOG4J2-2269): anks to Jonas Rutishauser.
MutableLogEvent references to other objects are cleared after each use. * [LOG4J2-2422](https://issues.apache.org/jira/browse/LOG4J2-2422):
Fix a memory leak causing references to parameters to be held after sync Handle some unchecked exceptions while loading plugins. Thanks to rswart, Gary G
hronous logging with thread locals enabled. regory.
* [LOG4J2-2301](https://issues.apache.org/jira/browse/LOG4J2-2301): * [LOG4J2-2441](https://issues.apache.org/jira/browse/LOG4J2-2441):
Mixed async loggers no longer forget parameter values, providing some appenders Setting a null ErrorHandler on AbstractAppender is not allowed and will no-op as
with an array of nulls. expected.
* [LOG4J2-2331](https://issues.apache.org/jira/browse/LOG4J2-2331): * [LOG4J2-2444](https://issues.apache.org/jira/browse/LOG4J2-2444):
RollingFileManager debug logging avoids string concatenation and errant braces i ErrorHandler is invoked with a LogEvent and Throwable when possible, where previ
n favor of parameterized logging. Thanks to Mike Baranski. ously only a string was used.
* [LOG4J2-2333](https://issues.apache.org/jira/browse/LOG4J2-2333): * [LOG4J2-2413](https://issues.apache.org/jira/browse/LOG4J2-2413):
Handle errors thrown in default disruptor ExceptionHandler implementations to av Exceptions are added to all columns when a JDBC Appender's ColumnMapping uses a
oid killing background threads. Pattern. Thanks to Andres Luuk, Gary Gregory.
* [LOG4J2-2334](https://issues.apache.org/jira/browse/LOG4J2-2334): * [LOG4J2-2466](https://issues.apache.org/jira/browse/LOG4J2-2466):
Add API org.apache.logging.log4j.core.appender.AsyncAppender.getQueueSize(). ColumnMapping literal not working. Thanks to Paolo Bonanomi, Gary Gregory.
* [LOG4J2-2336](https://issues.apache.org/jira/browse/LOG4J2-2336): * [LOG4J2-2478](https://issues.apache.org/jira/browse/LOG4J2-2478):
Remove duplicate hyphen from the AsyncLoggerConfig background thread name. AbstractStringLayoutStringEncodingBenchmark returns the computed variables on ea
* [LOG4J2-2347](https://issues.apache.org/jira/browse/LOG4J2-2347): ch benchmark to avoid DCE. Thanks to Diego Elias Costa.
Update Apache Commons Compress from 1.16.1 to 1.17. * [LOG4J2-2134](https://issues.apache.org/jira/browse/LOG4J2-2134):
* [LOG4J2-2352](https://issues.apache.org/jira/browse/LOG4J2-2352): StackOverflowError at AwaitCompletionReliabilityStrategy. Thanks to David del Am
RingBufferLogEvent memento messages provide the expected format string, and no l o Mateos, Gary Gregory.
onger attempt to substitute parameters into curly braces in parameter toString v * [LOG4J2-2481](https://issues.apache.org/jira/browse/LOG4J2-2481):
alues. Avoid NullPointerExceptions in org.apache.logging.log4j.core.config.AbstractConf
Both RingBufferLogEvent and MutableLogEvent memento implementations memo iguration for null arguments.
ize results to avoid rebuilding formatted string values. * [LOG4J2-2457](https://issues.apache.org/jira/browse/LOG4J2-2457):
* [LOG4J2-2355](https://issues.apache.org/jira/browse/LOG4J2-2355): RollingRandomAccessFileManager ignores new file patterns from programmatic recon
PropertiesUtil ignores non-string system properties. Fixes a NoClassDefFoundErro figuration. Thanks to Heiko Schwanke, Gary Gregory.
r initializing StatusLogger * [LOG4J2-2482](https://issues.apache.org/jira/browse/LOG4J2-2482):
caused by an NPE while initializing the static PropertiesUtil field. Tha BasicContextSelector cannot be used in a OSGI application. Thanks to Rob Gansevl
nks to Henrik Brautaset Aronsen. es.
* [LOG4J2-2362](https://issues.apache.org/jira/browse/LOG4J2-2362): * [LOG4J2-2476](https://issues.apache.org/jira/browse/LOG4J2-2476):
Fixed a memory leak in which ReusableObjectMessage would hold a reference to the org.apache.log4j.SimpleLayout and ConsoleAppender missing in log4j-1.2-api. Than
most recently logged object. ks to Al Bundy.
* [LOG4J2-2312](https://issues.apache.org/jira/browse/LOG4J2-2312): * [LOG4J2-2497](https://issues.apache.org/jira/browse/LOG4J2-2497):
Jackson layouts used with AsyncLoggerContextSelector output the expected format JmsAppender reconnectIntervalMillis cannot be set from a configuration file.
rather than only a JSON string of the message text. * [LOG4J2-2499](https://issues.apache.org/jira/browse/LOG4J2-2499):
* [LOG4J2-2364](https://issues.apache.org/jira/browse/LOG4J2-2364): JMS Appender may throw a NullPointerException when JMS is not up while the Appen
Fixed a memory leak in which ReusableParameterizedMessage would hold a reference der is starting.
to the most recently * [LOG4J2-2508](https://issues.apache.org/jira/browse/LOG4J2-2508):
logged throwable and provided varargs array. JDBC Appender fails when using both parameter, source, and literal ColumnMapping
* [LOG4J2-2368](https://issues.apache.org/jira/browse/LOG4J2-2368): elements.
Nested logging doesn't clobber AbstractStringLayout cached StringBuidlers * [LOG4J2-2527](https://issues.apache.org/jira/browse/LOG4J2-2527):
* [LOG4J2-2373](https://issues.apache.org/jira/browse/LOG4J2-2373): Prevent ConcurrentModificationException while iterating over ListAppender events
StringBuilders.escapeJson implementation runs in linear time. Escaping large JSO .
N strings * [LOG4J2-2522](https://issues.apache.org/jira/browse/LOG4J2-2522):
in EncodingPatternConverter and MapMessage will perform significantly be Fix regression using MapMessageLookup.lookup with MapMessages that do not implem
tter. Thanks to Kevin Meurer. ent StringMapMessage. Thanks to Adam Lesiak.
* [LOG4J2-2376](https://issues.apache.org/jira/browse/LOG4J2-2376): * [LOG4J2-2530](https://issues.apache.org/jira/browse/LOG4J2-2530):
StringBuilders.escapeXml implementation runs in linear time. Escaping large XML Generalize checks using MapMessage implementations with do not extend StringMapM
strings essage.
in EncodingPatternConverter and MapMessage will perform significantly be Introduce new JAVA_UNQUOTED MapMessage format type based on the JAVA for
tter. Thanks to Kevin Meurer. matting, but without
* [LOG4J2-2377](https://issues.apache.org/jira/browse/LOG4J2-2377): quoted values. Thanks to Travis Spencer.
NullPointerException in org.apache.logging.log4j.util.LoaderUtil.getClassLoaders * [LOG4J2-2533](https://issues.apache.org/jira/browse/LOG4J2-2533):
() when using Bootstrap class loader. Thanks to Mirko Rzehak, Gary Gregory. Fix a regression introduced by LOG4J2-2301 in 2.11.1 allowing allocation to occu
* [LOG4J2-2382](https://issues.apache.org/jira/browse/LOG4J2-2382): r in AsyncLoggerConfig. Thanks to Michail Prusakov.
Update Mongodb 3 driver from 3.6.3 to 3.8.0.
* [LOG4J2-2388](https://issues.apache.org/jira/browse/LOG4J2-2388):
Thread indefinitely blocked when logging a message in an interrupted thread. Tha
nks to Failled.
### Changes ### Changes
* [LOG4J2-1721](https://issues.apache.org/jira/browse/LOG4J2-1721): * [LOG4J2-1576](https://issues.apache.org/jira/browse/LOG4J2-1576):
Allow composite configuration for context parameter. Thanks to Phokham Nonava. Switch from CLIRR to RevAPI for detecting API changes.
* [LOG4J2-2302](https://issues.apache.org/jira/browse/LOG4J2-2302): * [LOG4J2-2391](https://issues.apache.org/jira/browse/LOG4J2-2391):
Status logger should show the Log4j name and version when initializing itself. Improve exception logging performance. ThrowableProxy construction uses a faster
* [LOG4J2-2304](https://issues.apache.org/jira/browse/LOG4J2-2304): method to discover the current stack trace. ThrowablePatternConverter an
Log4j2 2.8.2 JMX unregister NullPointerException. Thanks to wumengsheng. d
* [LOG4J2-2311](https://issues.apache.org/jira/browse/LOG4J2-2311): ExtendedThrowablePatternConverter default configurations no longer alloc
Update Jackson from 2.9.4 to 2.9.5. ate
* [LOG4J2-2313](https://issues.apache.org/jira/browse/LOG4J2-2313): an additional buffer for stack trace contents.
Update LMAX Disruptor from 3.3.7 to 3.4.2. * [LOG4J2-2447](https://issues.apache.org/jira/browse/LOG4J2-2447):
* [LOG4J2-548](https://issues.apache.org/jira/browse/LOG4J2-548): Let the NullAppender default its name to "null".
Log4j 2.0 ERROR "Could not search jar" with JBoss EAP 6.2. Thanks to Shehata, Pa * [LOG4J2-2468](https://issues.apache.org/jira/browse/LOG4J2-2468):
resh Varke, Eric Victorson, Martin Laforet. Update Jackson from 2.9.6 to 2.9.7.
* [LOG4J2-2328](https://issues.apache.org/jira/browse/LOG4J2-2328): * [LOG4J2-2469](https://issues.apache.org/jira/browse/LOG4J2-2469):
Update JAnsi from 1.17 to 1.17.1. Update Apache Commons Compress from 1.17 to 1.18.
* [LOG4J2-2351](https://issues.apache.org/jira/browse/LOG4J2-2351): * [LOG4J2-2470](https://issues.apache.org/jira/browse/LOG4J2-2470):
Added AbstractLogEvent.getMutableInstant to allow the MutableInstant instance to Update Apache Commons CSV from 1.5 to 1.6.
be modified by classes extending AbstractLogEvent. * [LOG4J2-2471](https://issues.apache.org/jira/browse/LOG4J2-2471):
* [LOG4J2-2357](https://issues.apache.org/jira/browse/LOG4J2-2357): Update javax.mail from 1.6.1 to 1.6.2.
Update Jackson from 2.9.5 to 2.9.6. * [LOG4J2-2472](https://issues.apache.org/jira/browse/LOG4J2-2472):
* [LOG4J2-2358](https://issues.apache.org/jira/browse/LOG4J2-2358): Update mongo-java-driver 3 from 3.8.0 to 3.8.2.
Update Kafka client from 1.0.0 to 1.1.0. * [LOG4J2-2489](https://issues.apache.org/jira/browse/LOG4J2-2489):
* [LOG4J2-2384](https://issues.apache.org/jira/browse/LOG4J2-2384): JDBC Appender should release parameter resources ASAP.
Update Kafka client from 1.1.0 to 1.1.1. * [LOG4J2-2491](https://issues.apache.org/jira/browse/LOG4J2-2491):
* [LOG4J2-2385](https://issues.apache.org/jira/browse/LOG4J2-2385): Allow all Appenders to optionally carry a Property array.
Update Groovy from 2.4.13 to 2.5.1. * [LOG4J2-2405](https://issues.apache.org/jira/browse/LOG4J2-2405):
* [LOG4J2-2386](https://issues.apache.org/jira/browse/LOG4J2-2386): Better handling of %highlight pattern when using jul-bridge. Thanks to Marco Her
Update optional Apache Commons DBCP from 2.2.0 to 2.4.0. rn.
* [LOG4J2-2503](https://issues.apache.org/jira/browse/LOG4J2-2503):
Update MongoDB driver from 3.8.2 to 3.9.0 for log4j-mongodb3 module.
--- ---
Apache Log4j 2.11.1 requires a minimum of Java 7 to build and run. Log4j 2.3 was the Apache Log4j 2.11.2 requires a minimum of Java 7 to build and run. Log4j 2.3 was the
last release that supported Java 6. last release that supported Java 6.
Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api compone nt, however it Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api compone nt, however it
does not implement some of the very implementation specific classes and methods. The package 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 a ny conflicts names and Maven groupId have been changed to org.apache.logging.log4j to avoid a ny conflicts
with log4j 1.x. with log4j 1.x.
For complete information on Apache Log4j 2, including instructions on how to sub mit bug For complete information on Apache Log4j 2, including instructions on how to sub mit bug
reports, patches, or suggestions for improvement, see the Apache Apache Log4j 2 website: reports, patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
 End of changes. 12 change blocks. 
155 lines changed or deleted 174 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)