Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 60CA210DC5 for ; Sun, 27 Oct 2013 17:57:35 +0000 (UTC) Received: (qmail 43803 invoked by uid 500); 27 Oct 2013 17:56:57 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 43688 invoked by uid 500); 27 Oct 2013 17:56:39 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 43659 invoked by uid 99); 27 Oct 2013 17:56:31 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Oct 2013 17:56:31 +0000 Date: Sun, 27 Oct 2013 17:56:31 +0000 (UTC) From: "Mike Drob (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (ACCUMULO-1242) Consistent logging MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned ACCUMULO-1242: ----------------------------------- Assignee: Mike Drob > Consistent logging > ------------------ > > Key: ACCUMULO-1242 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1242 > Project: Accumulo > Issue Type: Bug > Components: build > Reporter: Christopher Tubbs > Assignee: Mike Drob > Labels: log4j, logging, logs, slf4j > Fix For: 1.7.0 > > > Logging dependencies are very inconsistent. It seems we have absolute dependencies on log4j, yet use slf4j sometimes, and log4j other times. In some of our tests we have slf4j-nop as a test dependency. > It seems we could consolidate a lot of this if we simply did: > # slf4j-api : compile > # slf4j-log4j12 : runtime > # slf4j-nop : test > # log4j : runtime > We could do this in the parent POM and get rid of all the different dependencies throughout the code. > I don't know that we could ever use anything other than slf4j-log4j12 as the implementation (unless our dependencies broke away from using log4j directly also), but at least we'd clean up all the logging dependencies in our code/build, and would be ready to switch to something better if something came along. Further, if somebody wanted to reuse our code, and weren't tied to log4j, because they didn't need our transitive dependencies that locked in log4j, they could easily depend on their own slf4j implementation jar, and all the logging in our code would still work correctly for them without needing to use something like log4j-over-slf4j. -- This message was sent by Atlassian JIRA (v6.1#6144)