This class is not necessary to realize multi-thread model in SpotBugs 4.0. Each detector instance will
not run on multiple threads, then only database (or other classes shared by detectors) needs
synchronization and they can use normal Java synchronization instead.
AnnotationDatabases are being phased out, since annotations are
now stored directly in the XClass/XMethod/XField objects.
Resolving nullness annotations will be handled through the
JSR-305 type qualifier code.
The annotation based approach is useless for lambdas. Write expectations using edu.umd.cs.findbugs.test.matcher.BugInstanceMatcher matchers in test source directory
AnnotationDatabases are being phased out, since annotations are
now stored directly in the XClass/XMethod/XField objects.
Resolving nullness annotations will be handled through the
JSR-305 type qualifier code.
AnnotationDatabases are being phased out, since annotations are
now stored directly in the XClass/XMethod/XField objects.
Resolving nullness annotations will be handled through the
JSR-305 type qualifier code.
The annotation based approach is useless for lambdas. Write expectations using edu.umd.cs.findbugs.test.matcher.BugInstanceMatcher matchers in test source directory
The annotation based approach is useless for lambdas. Write expectations using edu.umd.cs.findbugs.test.matcher.BugInstanceMatcher matchers in test source directory
The annotation based approach is useless for lambdas. Write expectations using edu.umd.cs.findbugs.test.matcher.BugInstanceMatcher matchers in test source directory
The annotation based approach is useless for lambdas. Write expectations using edu.umd.cs.findbugs.test.matcher.BugInstanceMatcher matchers in test source directory
- use CheckForNull instead; the name of which more clearly
indicates that not only could the value be null, but that good
coding practice requires that the value be checked for null.