[
https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437854#comment-15437854
]
Matt Sicker edited comment on LOG4J2-1547 at 8/25/16 10:39 PM:
---------------------------------------------------------------
I know that log4j-core's APIs aren't strongly backwards compatible, but
AbstractConfiguration is one of the few classes that tend to get extended when
writing programmatic configuration. We even have examples on how to do it
(which you updated as well). Shouldn't some default (but deprecated) methods be
provided that tries to pull in the LoggerContext the old way? We could remove
the deprecated methods in 2.8 or 2.9, thus giving people time to migrate their
configurations.
was (Author: jvz):
I know that log4j-core's APIs are strongly backwards compatible, but
AbstractConfiguration is one of the few classes that tend to get extended when
writing programmatic configuration. We even have examples on how to do it
(which you updated as well). Shouldn't some default (but deprecated) methods be
provided that tries to pull in the LoggerContext the old way? We could remove
the deprecated methods in 2.8 or 2.9, thus giving people time to migrate their
configurations.
> 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]
