I’m unclear which sub-system to flag the problem as. I use the sonarqube plugin, but the errors are reported in sonarcloud. I’ll go out on a limb here, and assume that sonarcloud will just show what sonarqube outputs, and that the problem lies with Sonarqube
Have you tried setting this exclusion via the UI? Right now there are 2 questions: proper configuration of multi-value property; proper configuration of exclusion. Doing this via the UI will eliminate one of them.
I’ve just taken a closer look at your issue screenshots.
You’ve excluded the rule from running on files named LoggingFacade.kt regardless of which directory they’re in. But the issue is being raised not in LoggingFacade.kt but in UseCaseLoggingFacade.kt.
So I guess you’re looking for the pattern **/*LoggingFacade.kt.
You’re correct, when I use that, the exclusion added through the UI works. Thanks for that.
The UI way of doing this is not what I’m looking for though. I would like to achieve this using one of version controllable plain text means I mentioned in the topic subject. Can you speak to those?
Because multi-value properties are tricky to configure, we recommend you do that via the UI. But now that you’ve verified that you’ve got the right pattern, I suppose you can just move it back into your analysis config.
Yes, it was working for the rule I described in the comment prior (loggingFacadesShouldBeAllowedToHaveWeirdMethodNames). These systemProp prefixed variables are passed on to the JVM daemon that gradle spawns to run the actual command. So that part is working.
Because It works for loggingFacadesShouldBeAllowedToHaveWeirdMethodNames ( kotlin:S100) using the top-level gradle.properties, I expected it to work for common-kotlin:SkippedUnitTests, which it doesn’t. So I’m still stumped.