"If a worker wants to do his job well, he must first sharpen his tools." - Confucius, "The Analects of Confucius. Lu Linggong"
Front page > Programming > What are the Valid @SuppressWarnings Annotation Warning Names in Java?

What are the Valid @SuppressWarnings Annotation Warning Names in Java?

Published on 2024-11-17
Browse:996

What are the Valid @SuppressWarnings Annotation Warning Names in Java?

@SuppressWarnings Annotation Warning Names in Java

The @SuppressWarnings annotation, when applied to a code block, suppresses certain types of compiler warnings. The valid warning names that can be used within the @SuppressWarnings annotation vary depending on the IDE or compiler being used.

List of Valid Warning Names:

The following list includes valid warning names for Eclipse Galileo:

  • all: Suppresses all warnings.
  • boxing: Suppresses warnings related to boxing/unboxing operations.
  • cast: Suppresses warnings related to cast operations.
  • dep-ann: Suppresses warnings related to deprecated annotations.
  • deprecation: Suppresses warnings related to deprecation.
  • fallthrough: Suppresses warnings related to missing breaks in switch statements.
  • finally: Suppresses warnings related to finally blocks that do not return.
  • hiding: Suppresses warnings related to locals that hide variables.
  • incomplete-switch: Suppresses warnings related to missing entries in a switch statement (enum case).
  • nls: Suppresses warnings related to non-nls string literals.
  • null: Suppresses warnings related to null analysis.
  • restriction: Suppresses warnings related to usage of discouraged or forbidden references.
  • serial: Suppresses warnings related to missing serialVersionUID field for a serializable class.
  • static-access: Suppresses warnings related to incorrect static access.
  • synthetic-access: Suppresses warnings related to unoptimized access from inner classes.
  • unchecked: Suppresses warnings related to unchecked operations.
  • unqualified-field-access: Suppresses warnings related to unqualified field access.
  • unused: Suppresses warnings related to unused code.

Additional warning names were introduced in subsequent versions of Eclipse:

  • javadoc: Suppresses warnings related to Javadoc warnings (Indigo and later).
  • rawtypes: Suppresses warnings related to usage of raw types (Indigo and later).
  • static-method: Suppresses warnings related to methods that could be declared as static (Indigo and later).
  • super: Suppresses warnings related to overriding a method without super invocations (Indigo and later).
  • resource: Suppresses warnings related to usage of resources of type Closeable (Juno and later).
  • sync-override: Suppresses warnings due to missing synchronize when overriding a synchronized method (Juno and later).

It is important to note that the list of valid warning names may vary for different IDEs or compilers. Always consult the documentation provided by your IDE or compiler for the most up-to-date information on supported warning names.

Release Statement This article is reprinted at: 1729671257 If there is any infringement, please contact [email protected] to delete it
Latest tutorial More>

Disclaimer: All resources provided are partly from the Internet. If there is any infringement of your copyright or other rights and interests, please explain the detailed reasons and provide proof of copyright or rights and interests and then send it to the email: [email protected] We will handle it for you as soon as possible.

Copyright© 2022 湘ICP备2022001581号-3