You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by rg...@apache.org on 2021/11/13 08:17:04 UTC
[logging-log4j2] branch release-2.x updated: Add changes from PR #592
This is an automated email from the ASF dual-hosted git repository.
rgoers 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 de21b67 Add changes from PR #592
de21b67 is described below
commit de21b67d25487f4c8844a48730568e0df99440ae
Author: Ralph Goers <rg...@apache.org>
AuthorDate: Sat Nov 13 01:16:50 2021 -0700
Add changes from PR #592
---
src/site/xdoc/manual/configuration.xml.vm | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/site/xdoc/manual/configuration.xml.vm b/src/site/xdoc/manual/configuration.xml.vm
index 319b67c..e298599 100644
--- a/src/site/xdoc/manual/configuration.xml.vm
+++ b/src/site/xdoc/manual/configuration.xml.vm
@@ -56,6 +56,12 @@
and <a href="customconfig.html">Programmatic Log4j Configuration</a>.
</p>
<p>
+ All available formats are functionally equivalent. For example, a configuration file in XML can be
+ rewritten using the properties format (and the opposite) without any loss of functionality. However,
+ the hierarchical nature of a Log4j configuration can be captured better in formats which naturally
+ support nesting so XML, JSON, and YAML files, are usually easier to use.
+ </p>
+ <p>
Note that unlike Log4j 1.x, the public Log4j 2 API does not expose methods to add, modify or remove
appenders and filters or manipulate the configuration in any way.
</p>