[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823017#comment-15823017
]
Pushkar Raste commented on ZOOKEEPER-2342:
------------------------------------------
[~cnauroth] - I was not aware of this existing JIRA and I opened
ZOOKEEPER-2659. I have opened a pull request with the required changes. I
looked at patch you attached to this ticket and most of the changes we have
have made seem identical.
Would you mind taking a look at the PR and let me know if it looks good.
I have to clean the PR a bit, but logging functionality seems to be working
with log4j2.
> 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
(v6.3.4#6332)
