You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by gg...@apache.org on 2022/01/20 13:24:45 UTC
[logging-log4j2] 04/04: Log4j 1.2 bridge should allow property and XML attributes to start with either an upper-case or lower-case letter.
This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
commit b36f1cea95e3ff44bff239397d3aef042de99eea
Author: Gary Gregory <ga...@gmail.com>
AuthorDate: Thu Jan 20 08:24:35 2022 -0500
Log4j 1.2 bridge should allow property and XML attributes to start with
either an upper-case or lower-case letter.
For example, "target" vs. "Target" in
"log4j.appender.Console.Target=System.err"
Add tests from PR #707 by ppkarwasz.
---
src/changes/changes.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index c1ded31..f8f6112 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -133,6 +133,9 @@
<action dev="ggregory" type="fix" due-to="Gary Gregory">
Log4j 1.2 bridge now logs a warning instead of throwing an NullPointerException when building a Syslog appender with a missing "SyslogHost" param.
</action>
+ <action dev="ggregory" type="fix" due-to="Gary Gregory, ppkarwasz">
+ Log4j 1.2 bridge should allow property and XML attributes to start with either an upper-case or lower-case letter.
+ </action>
<action dev="ggregory" type="fix">
JndiManager reverts to 2.17.0 behavior: Read the system property for each call.
</action>