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 Fri, 26 Aug 2016 01:53:21 GMT

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

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

Well, my idea here was to deprecate for 2.7, include in the release notes that it's being
removed, and remove it in 2.8. I'm personally not really attached to the old way of doing
it (I usually use XML or YAML), I was just considering all use cases.

> 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