accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Coleman (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-3651) Replace log4j dependencies with slf4j where setLevel is not used.
Date Sat, 14 Mar 2015 03:12:38 GMT


Ed Coleman updated ACCUMULO-3651:
    Attachment: ACCUMULO-3651.2.patch

This file superceeds and completely replaces the ACCUMULO-3651.patch file submitted earlier.
 This file includes findbugs and checkstyle fixes that were detected after the previous file
had been submitted.

> Replace log4j dependencies with slf4j where setLevel is not used.
> -----------------------------------------------------------------
>                 Key: ACCUMULO-3651
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.7.0
>            Reporter: Ed Coleman
>            Assignee: Ed Coleman
>              Labels: patch
>             Fix For: 1.7.0
>         Attachments: ACCUMULO-3651.2.patch, ACCUMULO-3651.patch
> Because of the issues originally encountered where setLevel is used, I'm going to break
the task into a few sub-tasks that can be accomplished in stages.
> This is the first sub-task and will include converting to slf4j where setLevel is not
used (that will be handled separately, after more discussion) nor where dom manipulation is
used (tests if memory serves.) 
> This sub-task should allow us to move forward while deferring the harder situations for
later (and in other sub-tasks.)
> The work on this task will include some modification to log statements where exceptions
are thrown without a message (message is required by slf4j) This sub-task will not include
conversion to use {} parameter formatting optimization to avoid string concatenation - that
will be a follow on sub-task.  
> My rational for multiple sub-tasks it to allow the changes to be evaluated in isolation
so that if there are objections, the core issue of removing direct log4j dependencies can
continue to move forward.

This message was sent by Atlassian JIRA

View raw message