[
https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439174#comment-15439174
]
Remko Popma edited comment on LOG4J2-1547 at 8/26/16 2:47 PM:
--------------------------------------------------------------
You made the changes so you know better than me :-) but yes that sounds right.
When documenting where the LoggerContext comes from you ask "where should it
come from?", but we invoke these methods somehow. Surely we can at least
specify where we get it from...
was (Author: [email protected]):
You made the changes so you know better than me but yes that sounds right.
When documenting where the LoggerContext comes from you ask "where should it
come from?", but we invoke these methods somehow. Surely we can at least
specify where we get it from...
> The Core AbstractConfiguration should track its LoggerContext and add
> Configuration.getLoggerContext()
> ------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1547
> URL: https://issues.apache.org/jira/browse/LOG4J2-1547
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Attachments: logging-log4j2.patch
>
>
> The class in Core, {{AbstractConfiguration}}, should track its
> {{LoggerContext}} and provide it with a new API
> {{Configuration.getLoggerContext()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
