Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Fri, 12 Aug 2016 17:09:20 +0000 (UTC)
From: =?utf-8?Q?Mikael_St=C3=A5ldal_=28JIRA=29?= <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12920618.1449709171000.294286.1471021760855@Atlassian.JIRA>
In-Reply-To: <JIRA.12920618.1449709171000@Atlassian.JIRA>
References: <JIRA.12920618.1449709171000@Atlassian.JIRA> <JIRA.12920618.1449709171269@arcas>
Subject: [jira] [Commented] (ZOOKEEPER-2342) Migrate to Log4J 2.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 12 Aug 2016 17:09:22 -0000


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
15419142#comment-15419142 ]=20

Mikael St=C3=A5ldal commented on ZOOKEEPER-2342:
-------------------------------------------

Maybe this will be easier if you fix ZOOKEEPER-233 and provide separate ser=
ver and client artifacts.

> 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 t=
hat this also removed the Log4J SLF4J binding jar from the runtime classpat=
h.  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 re=
solving 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 migr=
ation to Log4J 2.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)