If a method has two (or more, presumably) @CheckForNull parameters, only checks one for null, then passes both values to @Nonnull method parameters, no bug is reported. See attached.
These results are as intended. The FindBugs null pointer analysis is designed to produce minimum false positives without requiring super sophisticated analysis.
In this case, the analysis assumes that the fullness of the parameters might be coupled, and thus doesn't report a null dereference warning here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
These results are as intended. The FindBugs null pointer analysis is designed to produce minimum false positives without requiring super sophisticated analysis.
In this case, the analysis assumes that the fullness of the parameters might be coupled, and thus doesn't report a null dereference warning here.