[
https://issues.apache.org/jira/browse/LOG4J2-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759298#comment-16759298
]
ASF subversion and git services commented on LOG4J2-2500:
---------------------------------------------------------
Commit 82df7bfb190fcad48ffd8daeff0dd85761e310e9 in logging-log4j2's branch
refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=82df7bf ]
LOG4J2-2500 and LOG4J2-2543 - Add log4j-to-slf4j to bom pom.xml. Document that
Properties element must be first
> Property substitution not working if <Properties> tag is not placed at the
> beginning of configuration
> -----------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2500
> URL: https://issues.apache.org/jira/browse/LOG4J2-2500
> Project: Log4j 2
> Issue Type: Documentation
> Components: Core
> Affects Versions: 2.11.1
> Environment: Any project with log4j using as configuration a file
> like the one attached as example.
> With this configuration, logs will be printed as ${defaultLayout} instead of
> the actual message.
> Reporter: Javier Armendáriz
> Priority: Minor
> Labels: configuration, xml
> Attachments: log4j2.xml
>
>
> Tweaking my log configuration I found out that if the <Properties> is not
> placed at the beginning of the config just after the <Configuration> tag, the
> property substitution is not performed at all.
> Looking at the documentation I haven't seen anything related to the ordering
> of the elements in the config files. If there's a good reason that the
> properties should be placed first place in configuration, it'd be a good idea
> to note it somewhere in the documentation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
