zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shannon Carey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2342) Migrate to Log4J 2.
Date Tue, 04 Apr 2017 18:08:42 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955532#comment-15955532

Shannon Carey commented on ZOOKEEPER-2342:

I second the advice of [~anomalizer], "Do not bundle any binding as part of non-server artifacts
a.k.a. libraries. This is a place where the power/choice should solely lie in the hands of
the person integrating the libraries into their applications."

Otherwise people who use a Zookeeper client in their code (and don't use log4j) have to add
exclusions for log4j & the slf4j-log4j12 binding in order to avoid the "SLF4J: Detected
both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, preempting StackOverflowError."
error caused by multiple bindings in their app. Well-behaved sl4j based libraries should only
have a test-scope or {{<optional>true</optional>}} dependency on slf4j bindings
& logger implementations.

> Migrate to Log4J 2.
> -------------------
>                 Key: ZOOKEEPER-2342
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 3.6.0
>         Attachments: ZOOKEEPER-2342.001.patch
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that this also
removed the Log4J SLF4J binding jar from the runtime classpath.  Without any SLF4J binding
jar available on the runtime classpath, it is impossible to write logs.
> This JIRA investigated migration to Log4J 2 as a possible path towards resolving the
bug introduced by ZOOKEEPER-1371.  At this point, we know this is not feasible short-term.
 This JIRA remains open to track long-term migration to Log4J 2.

This message was sent by Atlassian JIRA

View raw message