Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Sat, 7 Jul 2012 12:50:35 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: <942260355.18630.1341665435468.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <26764049.190791290146893475.JavaMail.jira@thor>
Subject: [jira] [Resolved] (MAPREDUCE-2193) 13 Findbugs warnings on trunk
 and branch-0.22
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J resolved MAPREDUCE-2193.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s:     (was: 0.24.0)

This issue has gone stale. Trunk and 0.22 have diverged so much that its best to have newer JIRAs tracking it - if problems still exist (I know trunk has no findbugs issue presently). Resolving as 'Not a Problem'.
                
> 13 Findbugs warnings on trunk and branch-0.22
> ---------------------------------------------
>
>                 Key: MAPREDUCE-2193
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2193
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Nigel Daley
>            Priority: Blocker
>         Attachments: findbugsWarnings.html, hadoop-findbugs-report.html, hadoop-findbugs-report.html, hadoop-findbugs-report.html, mapreduce.trunk.findbugs.r1.diff, mapreduce.trunk.findbugs.r2.diff, mapreduce.trunk.findbugs.r3.diff, mapreduce.trunk.findbugs.r4.diff, mapreduce.trunk.findbugs.r5.diff, mapreduce.trunk.findbugs.r5.diff, mapreduce.trunk.findbugs.r6.diff, mapreduce.trunk.findbugs.r7.diff
>
>
> There are 13 findbugs warnings on trunk.  See attached html file.  These must be fixed or filtered out to get back to 0 warnings.  The OK_FINDBUGS_WARNINGS property in src/test/test-patch.properties should also be set to 0 in the patch that fixes this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira