GitHub user romanso123 opened a pull request:
https://github.com/apache/logging-log4j2/pull/91
failing test - irregular log4j2.json nodes order
Failing test, showing that log4j2.json config file nodes specific order can
fail log4j2 framework functionality.
Test description:
"properties" node in resources/log4j2.json config file is the last node
(not regular json nodes order)
due to this, log4j2 framework doesn't act normally
this log msg is not printed correctly - "${layout}" is printed.
if we set "properties" node to be before "appenders" node, everything will
work as expected.
why would json-node order matter? the nodes order in a JSON shouldn't
matter ...
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/romanso123/logging-log4j2
failing_test_log4j2_json_nodes_order
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/91.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #91
----
commit b11df691d3e520e7a71d6fd4d0aada092545407a
Author: romanso <[email protected]>
Date: 2017-07-04T08:27:13Z
failing test - irregular log4j2.json nodes order
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
