[
https://issues.apache.org/jira/browse/LOG4J2-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469675#comment-17469675
]
Ralph Goers commented on LOG4J2-1540:
-------------------------------------
Not all classes in log4j-core are public, even if they are declared as public.
But in classes that should be considered internal we generally have a statement
such as in
[https://github.com/apache/logging-log4j2/blob/release-2.x/log4j-core/src/main/java/org/apache/logging/log4j/core/net/UrlConnectionFactory.java.]
AbstractManager is not one of those classes so its contract should have
remained and the old constructor marked deprecated.
Please create a Jira issue and reference this one as causing the breakage.
> 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)
