You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2019/07/28 03:30:00 UTC

[jira] [Resolved] (LOG4J2-2556) log4j-1.2-api works only with core

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

Ralph Goers resolved LOG4J2-2556.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.12.1

I have made Log4j Core optional at runtime. It is still required for the build and some functionality will be lost if it is not present but it should still be sufficient for most applications.

Please verify and close.

> log4j-1.2-api works only with core
> ----------------------------------
>
>                 Key: LOG4J2-2556
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2556
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: log4j 1.2 emulation
>    Affects Versions: 2.11.1
>            Reporter: Michael Lipp
>            Priority: Major
>             Fix For: 2.12.1
>
>
> The Logger implementation of log4j-1.2-api casts to org.apache.logging.log4j.core.LoggerContext. This works only if the provider of log4j(2) is the default ("core") provider. I have written my own provider that includes its own implementation of a LoggerContext (properly implementing "org.apache.logging.log4j.spi.LoggerContext", of course). So the cast fails.
> IMHO log4j-1.2-api should work with any implementation of a log4j(2) provider.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)