File exclusions

All versions of SonarLint will fetch file exclusions from the SonarQube or SonarCloud server when you bind a project or update a binding while running in Connected Mode. Check the SonarQube and SonarCloud documentation for information about setting your Analysis scope.

File exclusions in the IDE

Go to IntelliJ Settings > Tools > SonarLint > File Exclusions to define an exclusion pattern. SonarLint for IntelliJ will accept wildcard patterns as described in the SonarQube and SonarCloud documentation.

Wildcard patterns

The recognized path-matching patterns are defined using the following wildcards:

• *  Match zero or more characters (not including the directory delimiter,  / ).
• **  Match zero or more directory segments within the path.
• ?  Match a single character (not including the directory delimiter,  / ).

Wildcard examples

• The pattern  **/*.css
  • matches  anyDirectory/anyFile.css
  • doesn't match  org/sonar.api/MyBean.java
• The pattern  **/*Bean.java
  • matches  org/sonar.api/MyBean.java
  • doesn't match  org/sonar/util/MyDTO.java
• The pattern  **/*Bean?.java
  • matches  org/sonar/util/MyOtherBean1.java
  • doesn't match  org/sonar/util/MyOtherBean.java
• The pattern  org/sonar/*
  • matches  org/sonar/MyClass.java
  • doesn't match  org/sonar/util/MyClassUtil.java
• The pattern  org/sonar/**/*
  • matches  org/sonar/MyClass.java
  • doesn't match  org/radar/MyClass.java