You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by vy...@apache.org on 2021/01/09 16:14:42 UTC
[logging-log4j2] branch release-2.x updated: Update change log.
This is an automated email from the ASF dual-hosted git repository.
vy pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/release-2.x by this push:
new db3e85c Update change log.
db3e85c is described below
commit db3e85cfe4319d0161821d5495bc320c085e8a7f
Author: Volkan Yazici <vo...@gmail.com>
AuthorDate: Sat Jan 9 17:14:29 2021 +0100
Update change log.
---
src/changes/changes.xml | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 7fad886..3172f08 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -29,13 +29,26 @@
- "update" - Change
- "remove" - Removed
-->
- <release version="2.14.1" date="2020-MM-DD" description="GA Release 2.14.1">
+ <release version="2.14.1" date="2021-MM-DD" description="GA Release 2.14.1">
+ <action issue="LOG4J2-2972" dev="vy" type="fix">
+ Refactor AsyncAppender and AppenderControl for handling of Throwables.
+ </action>
+ <action issue="LOG4J2-2985" dev="vy" type="fix">
+ Add eventTemplateRootObjectKey parameter to JsonTemplateLayout.
+ </action>
+ <action issue="LOG4J2-2976" dev="ggregory" type="fix">
+ JdbcAppender composes an incorrect INSERT statement
+ without a ColumnMapping element.
+ </action>
<action dev="rgoers" type="update">
Update Spring dependencies to 5.3.2, Spring Boot to 2.3.6, and Spring Cloud to Hoxton.SR9
</action>
<action issue="LOG4J2-2974" dev="rgoers" type="fix">
Log4j would fail to initialize in Java 8 with log4j-spring-boot.
</action>
+ <action issue="LOG4J2-2967" dev="ckozak" type="fix">
+ Fix JTL parameter resolution for messages with too few parameters.
+ </action>
<action issue="LOG4J2-2962" dev="vy" type="add">
Enrich "map" resolver by unifying its backend with "mdc" resolver.
</action>