zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pushkar Raste (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated
Date Tue, 17 Jan 2017 13:38:26 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826059#comment-15826059

Pushkar Raste commented on ZOOKEEPER-2659:

[~fpj] - log4j 1.X is EOL and will not work with JDK1.9, we have to bite the bullet at some
point. I do understand concerns about making sure changes are as smooth as possible (or at
the least well document any backwards incompatible changes). 

I have chosen to to use xml configuration instead of using properties style config. I like
structured xml configs but if people have strong opinions on using properties style config,
 I will definitely look into making required changes.

To summarize except for the fact that custom log configs made by the system admins, would
need to updated with 'log4j 2'  equivalents, are there any other concerns?

> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> ----------------------------------------------------------------
>                 Key: ZOOKEEPER-2659
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
>             Project: ZooKeeper
>          Issue Type: Wish
>            Reporter: Pushkar Raste
>            Assignee: Pushkar Raste
>            Priority: Minor
>         Attachments: zk_log4j2_migration.patch
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. {{log4j 1.X}}
is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}

This message was sent by Atlassian JIRA

View raw message