JSL 1.7

Oracle文档提到:

unchecked:未选中的警告由字符串“unchecked”标识。 deprecation:当使用了带有@Deprecated注解的类型、方法、字段或构造函数时(即被重写、调用或引用名称)，Java编译器必须产生deprecation警告，除非:[…]在实体中使用@SuppressWarnings("deprecation")注释来抑制警告;或

然后解释了实现可以添加并记录它们自己的:

编译器供应商应该将他们支持的警告名称与这种注释类型结合起来记录。鼓励供应商合作，以确保相同的名称在多个编译器中工作。

JSL 1.7

Oracle文档提到:

unchecked:未选中的警告由字符串“unchecked”标识。 deprecation:当使用了带有@Deprecated注解的类型、方法、字段或构造函数时(即被重写、调用或引用名称)，Java编译器必须产生deprecation警告，除非:[…]在实体中使用@SuppressWarnings("deprecation")注释来抑制警告;或

然后解释了实现可以添加并记录它们自己的:

编译器供应商应该将他们支持的警告名称与这种注释类型结合起来记录。鼓励供应商合作，以确保相同的名称在多个编译器中工作。

我只想补充一点，在https://gist.github.com/vegaasen/157fbc6dce8545b7f12c上有一个IntelliJ抑制参数的主列表

它看起来相当全面。部分:

Warning Description - Warning Name

"Magic character" MagicCharacter 
"Magic number" MagicNumber 
'Comparator.compare()' method does not use parameter ComparatorMethodParameterNotUsed 
'Connection.prepare*()' call with non-constant string JDBCPrepareStatementWithNonConstantString 
'Iterator.hasNext()' which calls 'next()' IteratorHasNextCallsIteratorNext 
'Iterator.next()' which can't throw 'NoSuchElementException' IteratorNextCanNotThrowNoSuchElementException 
'Statement.execute()' call with non-constant string JDBCExecuteWithNonConstantString 
'String.equals("")' StringEqualsEmptyString 
'StringBuffer' may be 'StringBuilder' (JDK 5.0 only) StringBufferMayBeStringBuilder 
'StringBuffer.toString()' in concatenation StringBufferToStringInConcatenation 
'assert' statement AssertStatement 
'assertEquals()' between objects of inconvertible types AssertEqualsBetweenInconvertibleTypes 
'await()' not in loop AwaitNotInLoop 
'await()' without corresponding 'signal()' AwaitWithoutCorrespondingSignal 
'break' statement BreakStatement 
'break' statement with label BreakStatementWithLabel 
'catch' generic class CatchGenericClass 
'clone()' does not call 'super.clone()' CloneDoesntCallSuperClone

我最喜欢的是IntelliJ中的@SuppressWarnings(“WeakerAccess”)，当它认为你应该使用一个比你正在使用的更弱的访问修饰符时，它不会抱怨。为了支持测试，我们必须对一些方法进行公共访问，而@VisibleForTesting注释并不能阻止警告。

埃塔: “匿名者”在@MattCampbell链接的页面上评论了以下非常有用的注释:

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.

如果你在使用SonarLint， 尝试上面的方法或类的整个鱿鱼串: @SuppressWarnings(“乌贼:S1172”)

这似乎是一个更完整的列表，在那里我发现了一些特定于Android-Studio的警告，我在其他地方找不到(例如SynchronizeOnNonFinalField)

https://jazzy.id.au/2008/10/30/list_of_suppresswarnings_arguments.html

哦，现在SO的指导方针与SO的限制相反。 一方面，我应该复制列表，而不是只提供链接。 但另一方面，这将超过允许的最大字符数。所以让我们希望这个链接不会断裂。