Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 14 Mar 2015 00:09:38 +0000 (UTC)
From: "Ed Coleman (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12780235.1425703307000.91769.1426291778121@Atlassian.JIRA>
In-Reply-To: <JIRA.12780235.1425703307000@Atlassian.JIRA>
References: <JIRA.12780235.1425703307000@Atlassian.JIRA>
 <JIRA.12780235.1425703307017@arcas>
Subject: [jira] [Updated] (ACCUMULO-3651) Replace log4j dependencies with
 slf4j where setLevel is not used.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ed Coleman updated ACCUMULO-3651:
---------------------------------
    Labels: patch  (was: )
    Status: Patch Available  (was: Open)

This patch should cover all of the "easy" cases where log4j specific features are not used.

> Replace log4j dependencies with slf4j where setLevel is not used.
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-3651
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3651
>             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
>
>
> 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
(v6.3.4#6332)