Project: <<unnamed project>>
FindBugs version: 1.3.5
Code analyzed:
1046 lines of code analyzed, in 28 classes, in 1 packages.
Metric | Total | Density* |
---|---|---|
High Priority Warnings | 0.00 | |
Medium Priority Warnings | 5 | 4.78 |
Total Warnings | 5 | 4.78 |
(* Defects per Thousand lines of non-commenting source statements)
Warning Type | Number |
---|---|
Dodgy Warnings | 5 |
Total | 5 |
Click on a warning row to see full context information.
Code | Warning |
---|---|
DLS | Dead store to result in com.plumtree.taglib.ptui.TopBestBetSearchButtonTag.DisplayTag() |
DLS | Dead store to imgTBBButton in com.plumtree.taglib.ptui.TopBestBetSearchButtonTag.GetButtonImage(String) |
IC | Initialization circularity between com.plumtree.taglib.ptui.BasicSearchButtonTag and com.plumtree.taglib.ptui.SearchFormTag |
IC | Initialization circularity between com.plumtree.taglib.ptui.BasicSearchButtonTag and com.plumtree.taglib.ptui.TopBestBetSearchButtonTag |
IC | Initialization circularity between com.plumtree.taglib.ptui.SearchFormTag and com.plumtree.taglib.ptui.TopBestBetSearchButtonTag |
This instruction assigns a value to a local variable, but the value is not read or used in any subsequent instruction. Often, this indicates an error, because the value computed is never used.
Note that Sun's javac compiler often generates dead stores for final local variables. Because FindBugs is a bytecode-based tool, there is no easy way to eliminate these false positives.
A circularity was detected in the static initializers of the two classes referenced by the bug instance. Many kinds of unexpected behavior may arise from such circularity.