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 52C6010C2C for ; Thu, 9 Jan 2014 00:36:51 +0000 (UTC) Received: (qmail 39472 invoked by uid 500); 9 Jan 2014 00:36:50 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 39445 invoked by uid 500); 9 Jan 2014 00:36:50 -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 39435 invoked by uid 99); 9 Jan 2014 00:36:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 00:36:50 +0000 Date: Thu, 9 Jan 2014 00:36:50 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2160) Run findbugs for 1.6 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-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866112#comment-13866112 ] Christopher Tubbs commented on ACCUMULO-2160: --------------------------------------------- Do we really want PasswordToken to return a copy on getPassword()? Will that violate it's "Destroyable"-ness in any way (maybe when it's overridden)? I'm not sure. Just want to make sure we're not doing something we don't want to do. I also wonder how many of these changes can be represented as warnings in Eclipse (or your IDE of choosing) and whether we should make them standards. Eclipse may even support some of these things (like stripping redundant modifiers off interfaces) as save-actions. Also, I noticed that many changes here added trailing whitespace (including indented blank lines). In TestLruBlockCache (perhaps elsewhere also), it should probably have used JUnit's Assert.assertArrayEquals(), for more informative failure messages, rather than assertTrue(Arrays.equals()) It's curious that Math.abs was inline'd into the class. What's the reasoning for that in the examples? > Run findbugs for 1.6 > -------------------- > > Key: ACCUMULO-2160 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2160 > Project: Accumulo > Issue Type: Task > Reporter: Eric Newton > Assignee: Eric Newton > Fix For: 1.6.0 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)