[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197495#comment-15197495
]
Alan Scherger commented on ZOOKEEPER-2342:
------------------------------------------
[~fournc] so this is somewhat a bummer for me because I was hoping that with us
adopting a new logger I'd finally have a solution for the old SyslogAppender
exception-newline problem. for example:
http://stackoverflow.com/questions/33177076/escape-newlines-in-zookeeper-logs-using-log4j-1-2-syslogappender
I understand the backwards compatibility issues, they're valid, and we probably
should revert this patch -- it just begs the question though, what's the plan
to rip the bandaid off?
> 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
> Assignee: Chris Nauroth
> Priority: Blocker
> Fix For: 3.5.2, 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, the it is
> impossible to write logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
