[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419094#comment-15419094
]
Mikael Ståldal commented on ZOOKEEPER-2342:
-------------------------------------------
Hi,
I am member of Apache Logging project PMC.
Due to various issues in Log4j 1.2.x, it will no longer work in JDK9:
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008654.html
As Log4j 1.x is EOL
(https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces),
these issues will not be fixed. We suggest upgrading to Log4j 2.x, we can
offer help to do so.
> 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)
