hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J Chouraria (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2193) 13 Findbugs warnings on trunk and branch-0.22
Date Fri, 11 Feb 2011 18:22:57 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993622#comment-12993622
] 

Harsh J Chouraria commented on MAPREDUCE-2193:
----------------------------------------------

It may be ignored if it is acceptable to do so, but via the findbugs filter XML, there's no
way of doing selective-ignore without ignoring the whole field itself (no line number sub-filter
either). I don't think ignoring the fields forever would be a good idea for changes that are
yet to come in that class.

> 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
>            Assignee: Harsh J Chouraria
>            Priority: Blocker
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: findbugsWarnings.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
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message