Rather than repeating myself, I’ll just point to the past conversations
on this topic:
http://markmail.org/message/pg7p2khityg4bjya
http://markmail.org/message/taztvj2ms7x6tryb
This one is particularly interesting:
http://markmail.org/message/lthcstbbmhtbrsva
It more or less matches my own experience with FindBugs.
The only way to ensure zero FindBugs warnings is to enforce it in
continuous integration, just like we did about Checkstyle. But before
doing that, you’ll have to come up with a satisfying exclude file that
filters out uninteresting warnings, and get the community to agree on
it.
Vincent
On 15/06/14 17:03, Glenn Adams wrote:
I'm getting tired of fixing findbugs warnings that people are leaving in the
code base. I'm going to start inserting comments that will break
compiles/builds if people don't check and fix these. Today I see four new
warnings:
*Dodgy Warnings*
*Code*
*Warning*
*BC*
Unchecked/unconfirmed cast from org.apache.fop.fo.FONode to
org.apache.fop.fo.flow.MultiCase in
org.apache.fop.layoutmgr.LayoutManagerMapping$MultiCaseLayoutManagerMaker.make(FONode,
List)
*BC*
Unchecked/unconfirmed cast from org.apache.fop.fo.FONode to
org.apache.fop.fo.flow.MultiSwitch in
org.apache.fop.layoutmgr.LayoutManagerMapping$MultiSwitchLayoutManagerMaker.make(FONode,
List)
*BC*
Unchecked/unconfirmed cast from org.apache.fop.fo.FObj to
org.apache.fop.fo.flow.MultiSwitch in new
org.apache.fop.layoutmgr.MultiSwitchLayoutManager(FObj)
*RCN*
Redundant nullcheck of footnoteList, which is known to be non-null in
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(List,
List, LayoutContext)
