Github user jochenw commented on the issue:
https://github.com/apache/logging-log4j2/pull/91
Quoting Ralph Goers:
This is not a bug but is intentional. Log4j processes configuration files
from beginning to end. It does not scan the file twice as would be necessary if
no order was required. Properties MUST come first so that they can be used by
the configuration that follows. Because of that we will generate an error if
the properties are encountered after some other element is found.
---
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.
---
