[
https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471494#comment-17471494
]
Volkan Yazici commented on LOG4J2-3323:
---------------------------------------
Judging from the changes incorporated in LOG4J2-1540, {{LoggerContext}} became
a requirement for {{{}AbstractManager{}}}, hence the ctor signature change. If
I am not mistaken, I don't think {{AbstractManager(String)}} signature can be
provided without violating {{LoggerContext}} constraint. [~ggregory], do you
have an idea?
> Breaking change in AbstractManager
> ----------------------------------
>
> Key: LOG4J2-3323
> URL: https://issues.apache.org/jira/browse/LOG4J2-3323
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Ryan Schmitt
> Priority: Major
>
> Due to LOG4J2-1540, a breaking change was made to a protected constructor in
> a public class. The fix is to add a new constructor that has the old
> signature: {{protected AbstractManager(final String name)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
