What is the list of valid @SuppressWarnings warning names in Java?

Question

What is the list of valid @SuppressWarnings warning names in Java?

The bit that comes in between the ("") in @SuppressWarnings("").

Solution 1

It depends on your IDE or compiler.

Here is a list for Eclipse Galileo:

• all to suppress all warnings
• boxing to suppress warnings relative to boxing/unboxing operations
• cast to suppress warnings relative to cast operations
• dep-ann to suppress warnings relative to deprecated annotation
• deprecation to suppress warnings relative to deprecation
• fallthrough to suppress warnings relative to missing breaks in switch statements
• finally to suppress warnings relative to finally block that don’t return
• hiding to suppress warnings relative to locals that hide variable
• incomplete-switch to suppress warnings relative to missing entries in a switch statement (enum case)
• nls to suppress warnings relative to non-nls string literals
• null to suppress warnings relative to null analysis
• restriction to suppress warnings relative to usage of discouraged or forbidden references
• serial to suppress warnings relative to missing serialVersionUID field for a serializable class
• static-access to suppress warnings relative to incorrect static access
• synthetic-access to suppress warnings relative to unoptimized access from inner classes
• unchecked to suppress warnings relative to unchecked operations
• unqualified-field-access to suppress warnings relative to field access unqualified
• unused to suppress warnings relative to unused code

List for Indigo adds:

• javadoc to suppress warnings relative to javadoc warnings
• rawtypes to suppress warnings relative to usage of raw types
• static-method to suppress warnings relative to methods that could be declared as static
• super to suppress warnings relative to overriding a method without super invocations

List for Juno adds:

• resource to suppress warnings relative to usage of resources of type Closeable
• sync-override to suppress warnings because of missing synchronize when overriding a synchronized method

Kepler and Luna use the same token list as Juno (list).

Others will be similar but vary.

Solution 2

All values are permitted (unrecognized ones are ignored). The list of recognized ones is compiler specific.

In The Java Tutorials unchecked and deprecation are listed as the two warnings required by The Java Language Specification, therefore, they should be valid with all compilers:

Every compiler warning belongs to a category. The Java Language Specification lists two categories: deprecation and unchecked.

The specific sections inside The Java Language Specification where they are defined is not consistent across versions. In the Java SE 8 Specification unchecked and deprecation are listed as compiler warnings in sections 9.6.4.5. @SuppressWarnings and 9.6.4.6 @Deprecated, respectively.

For Sun's compiler, running javac -X gives a list of all values recognized by that version. For 1.5.0_17, the list appears to be:

• all
• deprecation
• unchecked
• fallthrough
• path
• serial
• finally

Solution 3

The list is compiler specific. But here are the values supported in Eclipse:

• allDeprecation deprecation even inside deprecated code
• allJavadoc invalid or missing javadoc
• assertIdentifier occurrence of assert used as identifier
• boxing autoboxing conversion
• charConcat when a char array is used in a string concatenation without being converted explicitly to a string
• conditionAssign possible accidental boolean assignment
• constructorName method with constructor name
• dep-ann missing @Deprecated annotation
• deprecation usage of deprecated type or member outside deprecated code
• discouraged use of types matching a discouraged access rule
• emptyBlock undocumented empty block
• enumSwitch, incomplete-switch incomplete enum switch
• fallthrough possible fall-through case
• fieldHiding field hiding another variable
• finalBound type parameter with final bound
• finally finally block not completing normally
• forbidden use of types matching a forbidden access rule
• hiding macro for fieldHiding, localHiding, typeHiding and maskedCatchBlock
• indirectStatic indirect reference to static member
• intfAnnotation annotation type used as super interface
• intfNonInherited interface non-inherited method compatibility
• javadoc invalid javadoc
• localHiding local variable hiding another variable
• maskedCatchBlocks hidden catch block
• nls non-nls string literals (lacking of tags //$NON-NLS-)
• noEffectAssign assignment with no effect
• null potential missing or redundant null check
• nullDereference missing null check
• over-ann missing @Override annotation
• paramAssign assignment to a parameter
• pkgDefaultMethod attempt to override package-default method
• raw usage a of raw type (instead of a parametrized type)
• semicolon unnecessary semicolon or empty statement
• serial missing serialVersionUID
• specialParamHiding constructor or setter parameter hiding another field
• static-access macro for indirectStatic and staticReceiver
• staticReceiver if a non static receiver is used to get a static field or call a static method
• super overriding a method without making a super invocation
• suppress enable @SuppressWarnings
• syntheticAccess, synthetic-access when performing synthetic access for innerclass
• tasks enable support for tasks tags in source code
• typeHiding type parameter hiding another type
• unchecked unchecked type operation
• unnecessaryElse unnecessary else clause
• unqualified-field-access, unqualifiedField unqualified reference to field
• unused macro for unusedArgument, unusedImport, unusedLabel, unusedLocal, unusedPrivate and unusedThrown
• unusedArgument unused method argument
• unusedImport unused import reference
• unusedLabel unused label
• unusedLocal unused local variable
• unusedPrivate unused private member declaration
• unusedThrown unused declared thrown exception
• uselessTypeCheck unnecessary cast/instanceof operation
• varargsCast varargs argument need explicit cast
• warningToken unhandled warning token in @SuppressWarnings

Sun JDK (1.6) has a shorter list of supported warnings:

• deprecation Check for use of depreciated items.
• unchecked Give more detail for unchecked conversion warnings that are mandated by the Java Language Specification.
• serial Warn about missing serialVersionUID definitions on serializable classes.
• finally Warn about finally clauses that cannot complete normally.
• fallthrough Check switch blocks for fall-through cases and provide a warning message for any that are found.
• path Check for a nonexistent path in environment paths (such as classpath).

The latest available javac (1.6.0_13) for mac have the following supported warnings

• all
• cast
• deprecation
• divzero
• empty
• unchecked
• fallthrough
• path
• serial
• finally
• overrides

Solution 4

A new favorite for me is @SuppressWarnings("WeakerAccess") in IntelliJ, which keeps it from complaining when it thinks you should have a weaker access modifier than you are using. We have to have public access for some methods to support testing, and the @VisibleForTesting annotation doesn't prevent the warnings.

ETA: "Anonymous" commented, on the page @MattCampbell linked to, the following incredibly useful note:

You shouldn't need to use this list for the purpose you are describing. IntelliJ will add those SuppressWarnings for you automatically if you ask it to. It has been capable of doing this for as many releases back as I remember.

Just go to the location where you have the warning and type Alt-Enter (or select it in the Inspections list if you are seeing it there). When the menu comes up, showing the warning and offering to fix it for you (e.g. if the warning is "Method may be static" then "make static" is IntellJ's offer to fix it for you), instead of selecting "enter", just use the right arrow button to access the submenu, which will have options like "Edit inspection profile setting" and so forth. At the bottom of this list will be options like "Suppress all inspections for class", "Suppress for class", "Suppress for method", and occasionally "Suppress for statement". You probably want whichever one of these appears last on the list. Selecting one of these will add a @SuppressWarnings annotation (or comment in some cases) to your code suppressing the warning in question. You won't need to guess at which annotation to add, because IntelliJ will choose based on the warning you selected.

Solution 5

I noticed that //noinspection can be auto-generated in IntelliJ

• make sure you have not already a plan @SuppressWarninigs before the statement
• Now you can auto-generate the specific //noinspection by hitting Alt+Enter when you have the warning selected and then use the right arrow key to see the Suppress for ... option

Ended up here when I wanted to suppress a "switch has too few case labels" warning from IntelliJ. I did not find a complete List for IntelliJ's @SuppressWarning support but //noinspection did the trick for me.

View more solutions

Comments

[Snicolas]

This question is really nice and answers are useful. If someone from the JCP looks at it, you should realize how messy it is to add a suppress warning. There is no convention on case, hyphen, camel case, it's just a plain mess, it would be lovely to standardize this.

[kevinarpe]

I see "ProhibitedExceptionDeclared" within Eclipse Collections Framework (org.eclipse.collections.impl.block.function.checked.Throwin‌​gFunction), and that is not listed below.

[Ron Tuffin]

The Eclipse list here looks to compiler flags and not SuppressWarning annotations (check the last part of the doc you linked).

[D. Wroblewski]

They are both. By setting the compiler flags you tell the compiler what kind of warnings you want. With the annotations you can suppress these warnings in specific places in your code.

[Peter Štibraný]

I think the list is shorter for Eclipse. See latest galileo docs, list of available tokens for SupressWarnings is explicit there: help.eclipse.org/galileo/index.jsp?topic=/…

[Jesper]

I tried @SuppressWarnings("raw") in Eclipse 3.5 and it does not work - I get a warning that it "raw" is not a valid value for this annotation.

[stu]

me too. Unfortunatel that the jsp support isn't as flushed out as the java support is.

[Jesse Jashinsky]

In what instances would suppressing a null warning be useful?

[par]

@Jesse: When the compiler is wrong (i.e. a "'Stupid Flanders' warning"). Try compiling: void foo( Object o ) { boolean b; if ( ( b = o == null ) ) o = new Object(); o.toString(); }. Some environments (e.g. NetBeans 7.3 w/ Java 6 JDK [1.6.0_41]) will generate "o possibly null" at the o.toString() call even though o can't be null at that point.

[K.C.]

@cletus : Is it possible to add types of warnings in eclipse? The problem is that one of our team members uses IntelliJ, and that IDE has other suppress warning types that give warnings in Eclipse :) In Eclipse Indigo you can set in the preferences: Ignore unused SuppressWarnings tokens, but that doesn't seem to work ...

[Kissaki]

semicolon does not seem to work in luna? :( Can someone verify if semicolon is indeed valid?

[matteo]

What's the value for suppressing the "synchronization on non-final field" warning?

[kbolino]

It is not true that unchecked is the only one endorsed by the standard; the very next section from the one you quoted says deprecation warnings should not be produced when "The use is within an entity that is annotated to suppress the warning with the annotation @SuppressWarnings("deprecation")"

[JPM]

You can add @SuppressWarnings("SwitchStatementWithTooFewBranches") for that as well.

[Mickäel A.]

Unfortunately the Supress for ... option when clicking ALT+ENTER is not always available

[ihebiheb]

links are broken

[Oliver Hausler]

//noinspection SwitchStatementWithTooFewBranches before the switch works as well for me.