[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074218#comment-15074218
]
Arvind Jayaprakash commented on ZOOKEEPER-2342:
-----------------------------------------------
Here are my specific suggestions:
* 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.
* The choice on the server side should be as follows
* Bind to log4j-v1 as part of patch releases on existing GA/supported branches
* Bind to the chosen, modern implementation on a new minor version build. I
guess everyone likes log4j-v2 and we shall let it be that way
* Provide adequate documentation on how to use some other binding of choice
for those users/admins who wish to bring in their favourite binding (logback
fans, put your hands up)
> 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)
