[jira] [Commented] (LOG4J2-3323) Breaking change in AbstractManager

["Ralph Goers (Jira)" <ji...@apache.org>]

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

Ralph Goers commented on LOG4J2-3323:
-------------------------------------

I started looking at this and while it could be fixed I am not sure it should be. The fix would be to have the constructor call LogManager.getLoggerContext() which may not be accurate. In addition, the breakage occurred almost 6 years ago. Fixing it now seems like closing the gate after all the cows have already left. Due to that I guess I am going to have to agree to close this as won't fix.

> 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.7#820007)