Recent versions of Sonarqube have a warning, that absolute file patterns shall be replaced by relative ones: https://github.com/SonarSource/sonarqube/blob/master/sonar-plugin-api/src/main/java/org/sonar/api/batch/fs/internal/PathPattern.java#L54
We have the use case of excluding generated code from scans. Right now that is done via multiple patterns like
Just removing the “file:” prefix totally does not work, since Sonarqube seems to treat the pattern
relative to the source folder of the Maven project being analyzed (i.e. it seems to look only at the package path to match the pattern and does not exclude any file). In our case that “src-gen” is the Maven project source folder, but the files do not get excluded with the shortened pattern. What do I miss?