rnveach

> The separation between IT and Test should atleast remain. > So you are ok to have files named as "Input{CheckName}CheckXxxx.java" If we are talking about in the IT tier,...

Missing code coverage would also impact jacoco, which is also checking code coverage. Is Jacoco reporting similar missing code coverage is pitest only alone?

https://checkstyle.org/config_annotation.html#SuppressWarningsHolder_Properties > The attribute is the fully qualified name of the Check and value is its alias. Documentation states that it must be the fully qualified name. What documentation may...

> Another example is what is the default behavior of this check with no aliases set. Looks like it does default to the simple check name as seen at: https://github.com/checkstyle/checkstyle/blob/399f1b48b79731d65e824eb927971ef6174c3463/src/main/java/com/puppycrawl/tools/checkstyle/checks/SuppressWarningsHolder.java#L161

@strkkk Current behavior says right now if the module name is supplied, it suppresses everything regardless if the IDs are different. See my code paste above.

TreeWalker is not responsible for printing violations of JDK version. Its purpose is to parse and pass the parsing results on. It can print violations for parsing errors or children...

I think I might like the idea of adding suppressions to the check itself, locking the 2 together ( https://github.com/checkstyle/checkstyle/issues/11340#issuecomment-1049579521 ). The only downside to that is there would need...

Sevntu and sonar is using `addAttribute`. Eclipse and maven are not.

No PRs referencing this issue should say "Closes" or "Fixes" until all checks are complete. Reviewers need to make sure this is the case in each PR.

@romani See PR https://github.com/checkstyle/checkstyle/pull/11652 to understand this point. Let me know if you could point to where the confusion may be. Tests should not pull information in from the config...