[
https://issues.apache.org/jira/browse/LOG4J2-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220459#comment-15220459
]
Zbynek Vyskovsky commented on LOG4J2-1336:
------------------------------------------
We cannot. This class (or actually an interface) is provided by legacy log4j
1.2 so it needs to be defined exactly like its original counterparty log4j 1.2
wrapper over log4j2, the same name, the same package and the same set of
methods with the same signature.
> LoggerFactory in 1.2 API module is not compatible with 1.2
> ----------------------------------------------------------
>
> Key: LOG4J2-1336
> URL: https://issues.apache.org/jira/browse/LOG4J2-1336
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.5
> Reporter: Zbynek Vyskovsky
> Labels: patch
> Fix For: 2.6
>
> Attachments: log4j-1.2-compatible-factory.diff
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> LoggerFactory from log4j 1.2 compatibility layer is not compatible with the
> original 1.2 version. Therefore software which creates its customized loggers
> is failing due to AbstractMethodError error.
> The fix is quite simple - just keep the original interface. The attached
> patch continues to support the current method too, but uses different
> interface name for the functionality so it doesn't clash with 1.2 API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
