You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ryan Schmitt (Jira)" <ji...@apache.org> on 2022/01/05 20:18:00 UTC

[jira] [Commented] (LOG4J2-1540) The Core AbstractManager should track its LoggerContext

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

Ryan Schmitt commented on LOG4J2-1540:
--------------------------------------

Why was a breaking change made to the constructor of {{AbstractManager}}, a public class? Should this class not be referenced outside of the project?

> The Core AbstractManager should track its LoggerContext
> -------------------------------------------------------
>
>                 Key: LOG4J2-1540
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1540
>             Project: Log4j 2
>          Issue Type: New Feature
>            Reporter: Gary D. Gregory
>            Assignee: Gary D. Gregory
>            Priority: Major
>             Fix For: 2.7
>
>
> The class in Core, {{AbstractManager}}, should track its {{LoggerContext}}.
> Add:
> {code:java}
>     /**
>      * Gets the logger context used to create this instance or null. The logger context is usually set when an appender
>      * creates a manager and that appender is given a Configuration. Not all appenders are given a Configuration by
>      * their factory method or builder.
>      * 
>      * @return the logger context used to create this instance or null.
>      */
>     public LoggerContext getLoggerContext()
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)