logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()
Date Thu, 25 Aug 2016 22:40:20 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437854#comment-15437854
] 

Matt Sicker commented on LOG4J2-1547:
-------------------------------------

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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message