[jira] [Updated] (LOG4J2-1336) LoggerFactory in 1.2 API module is not compatible with 1.2

["Matt Sicker (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker updated LOG4J2-1336:
--------------------------------
    Attachment: Re_use_LoggerAdapter.patch

Attached is an example of what I was talking about. I think log4j-1.2-api was the only bridged module that wasn't using LoggerAdapter in some form as of 2.5.

> 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: Re_use_LoggerAdapter.patch, 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