[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050022#comment-15050022
]
Arshad Mohammad commented on ZOOKEEPER-2342:
--------------------------------------------
Hi [~cnauroth], it is right that log4j dependency has been removed but this was
the intention of the ZOOKEEPER-1371 jira. May be we can document some where
that users have to put runtime library of the logging framework of their
choice. For example to use log4j user should put slf4j-log4j12-1.7.5.jar and
slf4j-log4j12-1.7.5.jar in <ZOOKEEPER_HOME>/lib
> ZooKeeper cannot write logs, because there is no SLF4J binding available on
> the runtime classpath.
> --------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Chris Nauroth
> Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> 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, the it is
> impossible to write logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
