[
https://issues.apache.org/jira/browse/LOG4J2-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182462#comment-15182462
]
Ralph Goers commented on LOG4J2-1050:
-------------------------------------
I have the same issue with this patch. It should be possible to add methods
without breaking compatibility and requiring every lookup to accept a
Configuration event if it doesn't need it.
> Add a Log4jLookup class to help write log files relative to log4j2.xml
> ----------------------------------------------------------------------
>
> Key: LOG4J2-1050
> URL: https://issues.apache.org/jira/browse/LOG4J2-1050
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
> Affects Versions: 2.3
> Environment: All
> Reporter: adam Retter
> Priority: Critical
> Fix For: 2.4, 2.4.1, 2.6
>
> Attachments:
> 0001-feature-Added-support-for-properties-interpolation-o.patch,
> fix-log4jlookup.patch, updated_fix-log4jlookup.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I attach a patch related to this mailing list post -
> http://mail-archives.apache.org/mod_mbox/logging-log4j-user/201506.mbox/%3CCAPK0icj%3DY3T9ptBGyGdgbHyMow_YWcfwC6UdLHS-QbgnBk8wkA%40mail.gmail.com%3E
> The patch makes the properties `log4j:configLocation` and
> `log4j:configParentLocation` available for substitution in the log4j
> configuration file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
