Project: <<unnamed project>>
FindBugs version: 1.3.5
Code analyzed:
1243 lines of code analyzed, in 29 classes, in 1 packages.
Metric | Total | Density* |
---|---|---|
High Priority Warnings | 2 | 1.61 |
Medium Priority Warnings | 10 | 8.05 |
Total Warnings | 12 | 9.65 |
(* Defects per Thousand lines of non-commenting source statements)
Warning Type | Number |
---|---|
Correctness Warnings | 1 |
Malicious code vulnerability Warnings | 6 |
Dodgy Warnings | 5 |
Total | 12 |
Click on a warning row to see full context information.
Code | Warning |
---|---|
EC | Call to equals() with null argument in com.plumtree.taglib.logic.SortTag.DisplayTag() |
Code | Warning |
---|---|
MS | com.plumtree.taglib.logic.AHierIndexDataTag.ATTRIB_INDEX isn't final but should be |
MS | com.plumtree.taglib.logic.ArithmeticOperators.ops should be package protected |
MS | com.plumtree.taglib.logic.BooleanOperators.ops should be package protected |
MS | com.plumtree.taglib.logic.ConcatTag.CONCAT_EXAMPLE isn't final but should be |
MS | com.plumtree.taglib.logic.IntOperators.ops should be package protected |
MS | com.plumtree.taglib.logic.StringOperators.ops should be package protected |
Code | Warning |
---|---|
IC | Initialization circularity between com.plumtree.taglib.logic.ForEachTag and com.plumtree.taglib.logic.SeparatorTag |
IC | Initialization circularity between com.plumtree.taglib.logic.IfFalseTag and com.plumtree.taglib.logic.IfTag |
IC | Initialization circularity between com.plumtree.taglib.logic.IfFalseTag and com.plumtree.taglib.logic.IfTrueTag |
IC | Initialization circularity between com.plumtree.taglib.logic.IfTag and com.plumtree.taglib.logic.IfTrueTag |
NP | Load of known null value in com.plumtree.taglib.logic.SortTag.DisplayTag() |
This method calls equals(Object), passing a null value as
the argument. According to the contract of the equals() method,
this call should always return false
.
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.
A mutable static field could be changed by malicious code or by accident from another package. The field could be made final to avoid this vulnerability.
A mutable static field could be changed by malicious code or by accident. The field could be made package protected to avoid this vulnerability.
The variable referenced at this point is known to be null due to an earlier check against null. Although this is valid, it might be a mistake (perhaps you intended to refer to a different variable, or perhaps the earlier check to see if the variable is null should have been a check to see if it was nonnull).