You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2016/03/29 22:09:25 UTC
[jira] [Commented] (LOG4J2-1336) LoggerFactory 1.2 API not really
compatible with 1.2
[ https://issues.apache.org/jira/browse/LOG4J2-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216757#comment-15216757 ]
Ralph Goers commented on LOG4J2-1336:
-------------------------------------
I am not sure I care for your alternate name, but I get the intent.
> LoggerFactory 1.2 API not really 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org