You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2019/04/11 21:16:40 UTC
[GitHub] [logging-log4j2] abysas commented on issue #223: [LOG4J2-2476]
missing classes for 1.2 compatibility
abysas commented on issue #223: [LOG4J2-2476] missing classes for 1.2 compatibility
URL: https://github.com/apache/logging-log4j2/pull/223#issuecomment-482317370
@rgoers, thank you for confirming about the compatibility mismatch. I was so happy seeing the v2.11.2 release notes about added `ConsoleAppender`. The [migration guide ](https://logging.apache.org/log4j/2.x/manual/migration.html) from Log4j 1.x clearly indicates that applications that want to successfully use `log4j-1.2-api.jar` bridge to replace Log4j, the application:
> ... must not access methods and classes internal to the Log4j 1.x implementation such as **Appenders**, LoggerRepository or Category's callAppenders method.
Based on this clear limitation, I didn't tried to suggest a replacement for `ConsoleAppender` in Log4j2 bridge. We have a 3rd party application, which use Log4j and instantiates `ConsoleAppender` with specific `Layout` supplied in constructor. To support this application along with Log4j2 bridge, in my project I added custom `ConsoleAppender` having the same package as original one of v1.2.
And to my dismay the added `ConsoleAppender` in v2.11.2 is incompatible with the original class - it breaks the workaround, as added incompatible `ConsoleAppender` clashes with v1.2 compatible `ConsoleAppender` I've added.
It becomes a blocker to us to upgrade to the Log4j2 v2.11.2+ version.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services