Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
There is no universal Java switch for disabling any static-analysis rule. First identify the analyzer and the exact rule ID in its diagnostic; then use that tool’s suppression syntax or configuration. Use a local annotation or comment for one justified exception, a filter for selected findings or files, and a rule-set change only when the team wants that rule disabled more broadly.
Identify the analyzer and the rule ID first
Look at the full build diagnostic, IDE inspection name, or analyzer report—not just the warning text. Copy the rule identifier exactly as that tool presents it. A Checkstyle check name, PMD rule name, SpotBugs bug-pattern code, and Error Prone check name are different identifiers and are not interchangeable.
Also establish where the analyzer runs and how it is configured. A source annotation may be ignored unless that analyzer supports it; an XML suppression file has no effect unless the build or analyzer loads it. Java’s @SuppressWarnings annotation applies to compiler-recognized warning categories. Compilers must ignore unrecognized warning names, although they may report them, so the annotation alone does not silence arbitrary third-party tools.
Choose the narrowest scope that fits
- One declaration or finding: Prefer an analyzer-specific source annotation or same-line comment when supported.
- Recurring pattern or selected locations: Use a rule-specific filter that also limits the match to the relevant class, file, line, or condition.
- Generated or third-party source: Exclude only its path or file pattern, not a broad package that also contains hand-written code.
- Rule unwanted across the project: Change the active rule set or turn off that rule in analyzer configuration. This removes its coverage from future code in that analysis scope too.
If the finding should remain visible but should not fail the build, adjust severity where the analyzer supports it rather than suppressing it altogether.
Suppress a compiler warning
Use the compiler’s actual warning category, such as unchecked or deprecation, at the narrowest effective declaration. Oracle notes that the suppression covers the annotated declaration and elements contained within it.
@SuppressWarnings("unchecked")
List<String> values = (List<String>) input;This example concerns a compiler warning; it does not by itself suppress findings from PMD, Checkstyle, SpotBugs, or Error Prone.
Suppress a PMD finding
PMD supports rule-specific annotations and same-line NOPMD comments. Use the PMD rule name and keep the annotation at the smallest useful declaration. See the PMD warning-suppression guide.
Recommended Free Tools
Rank #2
@SuppressWarnings("PMD.UnusedLocalVariable")
class Example {
void run() {
int value = 42;
}
}For a finding on a particular line, PMD expects the marker on that same line:
int value = 42; // NOPMD - used by framework reflectionFor recurring cases, ruleset configuration can use violationSuppressRegex or violationSuppressXPath. XPath suppression depends on the AST node reported by the rule. Avoid broad expressions beginning with //, which can match elsewhere in the file. PMD 7 uses XPath 3.1 rather than XPath 1.0; consult the PMD 7 migration guide when adapting older XPath filters. PMD 7.14.0 introduced UnnecessaryWarningSuppression as an experimental rule for detecting suppressions that no longer suppress a violation.
Suppress a Checkstyle finding
Checkstyle’s annotation support is not automatic: the configuration needs both SuppressWarningsHolder inside TreeWalker and SuppressWarningsFilter under Checker. Without both modules, a Java annotation will not suppress Checkstyle findings. The SuppressWarningsFilter documentation describes the wiring and naming behavior.
<module name="Checker">
<module name="TreeWalker">
<module name="SuppressWarningsHolder"/>
<module name="MemberName"/>
</module>
<module name="SuppressWarningsFilter"/>
</module>With that setup, a suppression can name the check, optionally using the checkstyle: prefix:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match@SuppressWarnings("checkstyle:membername")
int J;Check names are case-insensitive; dotted prefixes and a trailing Check are removed for matching.
For centralized file, check, line, or column matching, configure a separate suppression XML with SuppressionFilter. Its specified attributes must all match, and check and file fields accept patterns.
Rank #4
<suppressions>
<suppress checks="MagicNumber" files="LegacyConverter\.java" lines="221,250-295"/>
</suppressions>For the Maven Checkstyle plugin, set suppressionsLocation so the suppression file is available to Checkstyle; see the check goal parameters. Comment-based filters such as SuppressionCommentFilter also require configuration. Do not assume markers such as CHECKSTYLE:OFF work by default or have the intended check scope.
Suppress a SpotBugs finding
SpotBugs provides @SuppressFBWarnings, with values that can identify a category, kind, or bug pattern, plus a justification field. Its annotations manual currently documents an annotations dependency at version 4.10.4; use a version compatible with the SpotBugs setup in your project rather than copying that version blindly.
import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
@SuppressFBWarnings(
value = "EI_EXPOSE_REP",
justification = "The public API intentionally exposes this view"
)
public List<String> values() {
return values;
}Check matching behavior before using a shortened pattern. The current annotation source documents prefix matching by default: EI_EXPO, for example, can match both EI_EXPOSE_REP and EI_EXPOSE_REP2. Current annotations support matchType=EXACT or REGEX for more controlled matching; confirm your installed annotations version supports the option before relying on it. The 4.9.4 API documentation is useful for checking behavior in that release.
Best Value
For report-level exclusions, SpotBugs filter XML can match bug patterns and classes, methods, or sources. A <Match> combines its child predicates, so the example below requires both the pattern and class to match. See the filter manual.
<FindBugsFilter>
<Match>
<Bug pattern="EI_EXPOSE_REP"/>
<Class name="com.example.LegacyApi"/>
</Match>
</FindBugsFilter>Pass a filter to the command line with -exclude. For Maven, the SpotBugs plugin provides excludeFilterFile; its Maven guide covers plugin configuration.
Disable or suppress an Error Prone check
Error Prone uses check names in compiler flags. Set a check to OFF to disable it, or use WARN or ERROR to change severity. If multiple flags set the same check, the last one wins. Current syntax is documented in Error Prone’s command-line flags guide.
-Xep:ReferenceEquality:OFFTo suppress one diagnostic locally, use @SuppressWarnings("CheckName") only when that check permits suppression. Check its documentation and the BugPattern API; individual checks can define suppression behavior.
-XepExcludedPaths takes a regular expression but excludes matching files from all Error Prone checks, not just one rule. It is therefore a much broader choice than turning off a named check. The obsolete -Xepdisable:<checkName> form is no longer supported.
Verify the exception and keep it maintainable
- Run the same analyzer and build task used in normal project checks; confirm the intended finding disappears and nearby findings still appear.
- Inspect annotation scope, line ranges, file patterns, regular expressions, and prefix matching for unintended matches.
- Put a short reason beside a source suppression or in the filter’s maintenance context so a reviewer can understand why it is necessary.
- Revisit line- and path-based entries after refactoring; they can stop matching or start covering different code.
- Remove suppressions when the underlying code or rule configuration changes. PMD’s experimental unused-suppression rule and SpotBugs’ bug descriptions can help with review, but a clean run and code review remain important.
If the analyzer reports a genuine defect, fix the code where practical or adjust a supported rule property to reflect the project’s requirements. Suppress only a justified exception, since a suppressed result is no longer surfaced by that analyzer.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
