[
https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474990#comment-17474990
]
Ryan Schmitt edited comment on LOG4J2-3323 at 1/12/22, 10:16 PM:
-----------------------------------------------------------------
I found this incompatibility while mass-upgrading my company to Log4j 2.17.
Someone had written an extension that depended on the old constructor signature.
was (Author: rschmitt):
I found this upgrade while mass-upgrading my company to Log4j 2.17. Someone had
written an extension that depended on the old constructor signature.
> 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)
