[
https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437926#comment-15437926
]
Gary Gregory commented on LOG4J2-1547:
--------------------------------------
Hi,
WRT "We could remove the deprecated methods in 2.8 or 2.9, thus giving people
time to migrate their configurations", I do not think that quite makes sense:
Either (1) a method is deprecated and removed in the next major version, or,
(2) it goes away before a major release or and breaks BC, so "giving people
time" does not do anything, it just delays the breakage, which will happen
anyway in case 2, and we have no control of which version folks will move from
and to.
G
> 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]
