You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/06/11 06:02:00 UTC

[jira] [Resolved] (ACCUMULO-3955) switch off of log4j v1.x

     [ https://issues.apache.org/jira/browse/ACCUMULO-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-3955.
-----------------------------------------
       Resolution: Incomplete
    Fix Version/s:     (was: 2.0.0)

As of 2.0, we are on a path to remove log4j1 references, but because some occurrences of Log4j were in the public API, they need to be deprecated first before removal (unfortunately). Further work can track this issue at https://github.com/apache/accumulo/issues

> switch off of log4j v1.x
> ------------------------
>
>                 Key: ACCUMULO-3955
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3955
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Mike Drob
>            Priority: Major
>
> 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
(v7.6.3#76005)