maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MCHECKSTYLE-405) The checkstyle plugin should report the number of all violations
Date Wed, 09 Jun 2021 18:39:00 GMT

    [ https://issues.apache.org/jira/browse/MCHECKSTYLE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360279#comment-17360279
] 

Guillaume Nodet commented on MCHECKSTYLE-405:
---------------------------------------------

The main problem is actually caused by the {{violationSeverity}} configuration parameter which
silently ignores some violations.  Any file containing a violation can not be cached by checkstyle,
so the result is that the user does not see any violation, but files are not cached.

> The checkstyle plugin should report the number of all violations
> ----------------------------------------------------------------
>
>                 Key: MCHECKSTYLE-405
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-405
>             Project: Maven Checkstyle Plugin
>          Issue Type: Improvement
>            Reporter: Guillaume Nodet
>            Priority: Major
>
> When there is an error, the build looks like:
> {code:java}
> [INFO] There is 1 error reported by Checkstyle 8.41.1 with config/maven_checks.xml ruleset.
> [ERROR] src/main/java/org/apache/maven/execution/BuildResumptionDataRepository.java:[54,30]
(whitespace) ParenPad: '(' is not followed by whitespace.
>  {code}
> and when this error is fixed, the build then looks like:
> {code}
> [INFO] You have 0 Checkstyle violations.
> {code}
> The problem is that checkstyle never caches the results for files with violations, even
at info or warning level.  This cause the files to be always processed, without the user really
being aware of any problem.
> The number of violations at info or warning level should also be printed.  In addition,
if there are errors, the output should be logged at WARN level.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message