Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: ctubbsii <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-134-accumulo@git.apache.org>
In-Reply-To: <git-pr-134-accumulo@git.apache.org>
Subject: [GitHub] accumulo issue #134: ACCUMULO-4391 Source deepcopies cannot be used safely i...
Content-Type: text/plain
Message-Id: <20160909015836.60A2FE03E2@git1-us-west.apache.org>
Date: Fri,  9 Sep 2016 01:58:36 +0000 (UTC)
archived-at: Fri, 09 Sep 2016 01:58:38 -0000

Github user ctubbsii commented on the issue:

    https://github.com/apache/accumulo/pull/134
  
    I agree with @EdColeman that we should avoid the direct use of Log4J in code. It looks like we're just doing it in a test, which is probably fine. I'm certainly not concerned about that in the 1.6 branch, though. We can address it in newer branches.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---