accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3955) switch off of log4j v1.x
Date Thu, 06 Aug 2015 22:21:28 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660887#comment-14660887
] 

Christopher Tubbs commented on ACCUMULO-3955:
---------------------------------------------

+1 to the proposal.

As for how to do it, I think we could do it if we use the 1-to-2 bridge, and include the needed
jars in our tarball. We do have to be careful about excluding any log4j 1.x jars from Hadoop
and other dependencies on the classpath. We'd definitely have to mention it in the release
notes for anybody upgrading to know to modify their classpath to exclude log4j 1.x. Further
transitioning to slf4j will, of course, help.

The biggest problems I think we'd run into is the custom log initialization stuff we're still
doing with the custom log4j configuration files (ACCUMULO-3546). I'm not sure we'd be able
to continue to maintain that well with log4j2 (needs investigation).

> switch off of log4j v1.x
> ------------------------
>
>                 Key: ACCUMULO-3955
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3955
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Mike Drob
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> log4j v1 is officially declared EOL, so we should clean up any remaining tasks and upgrade
to something else. log4j2 and logback are both reasonable options, since slf4j should be doing
most of the heavy lifting for us already.



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

Mime
View raw message