Deprecated API
Contents
- Interfaces
- Classes
- Enums
- Annotation Types
- Fields
- Methods
- Constructors
- Enum Constants
- Annotation Type Elements
-
Deprecated Interfaces
-
Deprecated ClassesClassDescriptionAnnotationDatabases 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.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.
-
Deprecated Enums
-
Deprecated Annotation TypesAnnotation TypeDescription- use
CheckForNullinstead.- useCheckReturnValueinstead.- Use the JSR305 annotations instead. For example, you can useParametersAreNonnullByDefaultinstead of @DefaultAnnotation(NonNull.class) so that method parameters are nonnull by default in the annotated element. You can also useTypeQualifierDefaultin general to define your own annotation that specifies a default type qualifier. For example,NonnegativeTypeQualifierDefault(ElementType.PARAMETER) public @interface ParametersAreNonnegativeByDefault {}The JSR305
CheckReturnValueannotation can be applied to a type or package, and it will act as a default for all methods in that class or package unless otherwise overridden.- use the JSR305 annotations instead, For example, you can useParametersAreNonnullByDefaultinstead of @DefaultAnnotation(NonNull.class), andTypeQualifierDefaultin general to define a type qualifier default. The JSR305CheckReturnValueannotation can be applied to a type or package, and it will act as a default for all methods in that class or package unless otherwise overridden.- useNonnullinstead.- useNullableinstead.- UseOverridingMethodsMustInvokeSuperinstead- 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.- UseSuppressFBWarningsinstead
-
Deprecated FieldsFieldDescription- use Builder instead
-
Deprecated MethodsMethodDescription- use confidence insteadcall getLabel() insteadedu.umd.cs.findbugs.ba.Hierarchy.findXMethod
(JavaClass[], String, String, JavaClassAndMethodChooser) UseDescriptorFactory.getClassDescriptor(ObjectType)insteadUseDescriptorFactory.createClassDescriptor(String)insteadUseDescriptorFactory.isClassResource(String)insteadUseUnreadFieldsData.getReadFields()insteadUseUnreadFieldsData.getWrittenFields()insteadUseUnreadFieldsData.isContainerField(XField)insteadUseUnreadFieldsData.isReflexive(XField)insteadUseUnreadFieldsData.isWrittenInConstructor(XField)insteadUse createDetector2 in new codeUseFBFrame.setFontSizeHelper(float,Component[])insteadUseClassName.matchedPrefixes(String[],String)insteadcall instantiateDetector2sInPass() insteadFindBugs2 and ClassPathBuilder take care of this automaticallyUseSystemProperties.getInt(String,int)instead
-
Deprecated ConstructorsConstructorDescriptionUse
PluginLoader(URL,URI,ClassLoader,boolean,boolean)instead
-
Deprecated Enum Constants
-
Deprecated Annotation Type ElementsAnnotation Type ElementDescription- use confidence instead