Custom rule, circumvent sonar.exclusions?


let’s say i want to write a custom java rule that is so important, that excluded sources should also
be scanned, because sonar.exclusions can also be used as a scanner property to hide code.

One could use a second analysis with a custom quality profile only containing those custom rules and overwrite sonar.exclusions, but that would always require a second analysis.

Is there another way via api when creating a custom java rule ?


Hi @Rebse,

The exclusions are defined for the full scope of the scan and can’t be overridden by a rule.


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.