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 161DE11A6F for ; Fri, 22 Aug 2014 23:34:12 +0000 (UTC) Received: (qmail 22199 invoked by uid 500); 22 Aug 2014 23:34:11 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 22142 invoked by uid 500); 22 Aug 2014 23:34:11 -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 21766 invoked by uid 99); 22 Aug 2014 23:34:11 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2014 23:34:11 +0000 Date: Fri, 22 Aug 2014 23:34:11 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-3081) ServerConfigurationFactoryTest is full of commented out and unused code MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Christopher Tubbs created ACCUMULO-3081: ------------------------------------------- Summary: ServerConfigurationFactoryTest is full of commented out and unused code Key: ACCUMULO-3081 URL: https://issues.apache.org/jira/browse/ACCUMULO-3081 Project: Accumulo Issue Type: Sub-task Reporter: Christopher Tubbs Priority: Minor Fix For: 1.6.1, 1.7.0 Commented out code is not good to leave in. It creates readability and maintainability problems, such as questions about how current it is, and whether the reasons for commenting it out are still valid. This code should be removed from ServerConfigurationFactoryTest. If there is a unit test which is broken in some way and needs to be disabled until some other problem is fixed, it should reference the relevant JIRA (ideally, which references the relevant code in return, so any contributor working on that issue knows it's there) and use the @Ignore annotation to disable. -- This message was sent by Atlassian JIRA (v6.2#6252)