You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Turner (JIRA)" <ji...@apache.org> on 2018/12/31 19:54:00 UTC

[jira] [Updated] (MCHECKSTYLE-365) In the Rules section of the site report, violation counts are grouped together incorrectly for rules of the same type and message but with different severity levels

     [ https://issues.apache.org/jira/browse/MCHECKSTYLE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Turner updated MCHECKSTYLE-365:
--------------------------------------
    Attachment: Screen Shot 2018-12-31 at 14.43.18.png

> In the Rules section of the site report, violation counts are grouped together incorrectly for rules of the same type and message but with different severity levels
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCHECKSTYLE-365
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-365
>             Project: Maven Checkstyle Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Robert Turner
>            Priority: Trivial
>         Attachments: Screen Shot 2018-12-31 at 14.43.18.png
>
>
> When the site report is generated, in the Rules section, the plug-in groups together the violation counts for rules that have the same name and message, but that have different severity levels. This results in both rules being listed, but with the same counts (which is incorrect).
> To be correct, the report should use the same criteria for determining unique rules as it does for aggregating the violation counts.
> A simple user work-around is to change the message for each of the rules with different severity levels. However, it's easy enough to fix in the plug-in as well.
> I will attach a screenshot of the issue manifesting itself, and I will attach a proposed patch (which I can convert into a PR if the maintainers deem this to be the right approach to solving this issue).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)