This is an automated email from the ASF dual-hosted git repository.
grobmeier pushed a commit to branch 2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/2.x by this push:
new 7f72db3a65 recommended migration of legacy components in some cases
first
7f72db3a65 is described below
commit 7f72db3a65b420b9141c9ee114e0a7748b88bb02
Author: Christian Grobmeier <[email protected]>
AuthorDate: Tue Aug 8 21:31:37 2023 +0200
recommended migration of legacy components in some cases first
---
src/site/markdown/log4j-1.2-api.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/site/markdown/log4j-1.2-api.md
b/src/site/markdown/log4j-1.2-api.md
index c608ec013e..86d823002d 100644
--- a/src/site/markdown/log4j-1.2-api.md
+++ b/src/site/markdown/log4j-1.2-api.md
@@ -53,5 +53,6 @@ running the following command in your terminal:
This command will generate a dependency tree for your project and filter the
results to show only Log4j 1.x dependencies.
If you find any, you will need to update your pom.xml file to remove Log4j1 or
exclude them otherwise.
-However, applications that try to modify legacy Log4j by adding Appenders,
Filters, etc, may experience problems.
-Most methods of this bridge are not doing anything.
+While we have improved the compatibility of the bridge in the past,
applications that try to modify legacy Log4j
+by adding Appenders, Filters, etc, may experience problems. In this case,
migrating those components to Log4j 2
+first is recommended.
