Never use deprecated fields, methods, or classes in new code. Java provides an
@deprecated annotation to indicate the deprecation of specific fields, methods, and classes. For example, many methods of
java.util.Date, such as
Date.getYear(), have been explicitly deprecated. THI05-J. Do not use Thread.stop() to terminate threads describes issues that can result from using the deprecated
The Java SE documentation provides a list of deprecated APIs for each version of the language:
Programmers should use the list of deprecated functions specific to the language version they are using, although it may also be possible to avoid the use of APIs that are deprecated in later versions as well if suitable alternatives are available.
Obsolete fields, methods, and classes should not be used. Java lacks any annotation that indicates obsolescence; nevertheless, several classes and methods are documented as obsolete. For instance, the
java.util.Dictionary<K,V> class is marked as obsolete; new code should use
java.util.Map<K,V> instead [API 2014].
Obsolete Methods and Classes
The methods and classes listed in the following table must not be used:
Class or Method
|java.util.Date||java.time (since Java 8)|
The Java Virtual Machine Profiler Interface (JVMPI) and JVM Debug Interface (JVMDI) are also deprecated and have been replaced by the JVM Tool Interface (JVMTI) (see ENV05-J. Do not deploy an application that can be remotely monitored for more information).
Using deprecated or obsolete classes or methods in program code can lead to erroneous behavior.
Detecting uses of deprecated methods is straightforward. Obsolete methods have no automatic means of detection.
|S1874||"@Deprecated" code should not be used|
Android Implementation Details
The Android SDK has deprecated and obsolete APIs. Also, there may exist incompatible APIs depending on the SDK version. Consequently, it is recommended that developers refer to the "Android API Differences Report" and consider replacing deprecated APIs.