rnveach

I think the issue centers around having an open ticket and changing master directly, and then adding a new commit to the ticket but not rebasing it off master the...

We are seeing a similar issue in Checkstyle with the `Line Coverage` column. Package summary says 100%, one file says 95% and the rest of the package (21 other files)...

> use maxSurviving = 0 This and your response is for max surviving mutants. I was talking about missed code coverage. There is no similar option in pitest for code...

@hcoles Thanks for the reply. I did not realize that was what the historic releases were for. Is there a list somewhere of what is needed to downloaded from maven...

@roeeduv I added your comment to the zip link. This means it isn't a complete workaround by itself, and is also disconnected from the updated configuration checkstyle provides every release...

The update causes the following violations (no suppressions): ```` [INFO] --- maven-pmd-plugin:3.10.0:check (default) @ checkstyle-sonar-plugin --- [INFO] PMD Failure: o.s.p.c.CheckstyleAuditListener:43 Rule:CommentRequired Field comments are required. [INFO] PMD Failure: o.s.p.c.CheckstyleAuditListener:45 Rule:CommentRequired...

This issue is not complete. Suppressions were added to speed up fixing TC. https://github.com/checkstyle/sonar-checkstyle/blob/master/checkstyle-sonar-plugin/config/pmd-main.xml#L12 https://github.com/checkstyle/sonar-checkstyle/blob/master/checkstyle-sonar-plugin/config/pmd-test.xml#L54

@romani Is it possible to put sonar as part of CI so we can see violations are fixed and won't come back?

IMO, I would start by updating https://github.com/checkstyle/eclipse-cs/blob/master/config/checkstyle_checks.xml to be the configuration you wish to be use for all of eclipse-cs. It is already controlled by CI, so the only thing...

@Bananeweizen Do you have time to rebase this and resolve the conflicts?