You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Schaefer (JIRA)" <ji...@codehaus.org> on 2013/07/31 20:50:54 UTC
[jira] (MCHECKSTYLE-182) Use Maven log levels when logging to
console
[ https://jira.codehaus.org/browse/MCHECKSTYLE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Schaefer updated MCHECKSTYLE-182:
--------------------------------------
Attachment: patch.diff
This patch will allow Checkstyle severity levels to map to Maven log levels.
> Use Maven log levels when logging to console
> --------------------------------------------
>
> Key: MCHECKSTYLE-182
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-182
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
> Affects Versions: 2.9.1
> Reporter: Andreas Sewe
> Priority: Minor
> Attachments: patch.diff
>
>
> Getting {{checkstyle:check}} to print out Checkstyle's findings to the console during a build is surprisingly hard/ugly:
> {code:xml}
> <violationSeverity>info</violationSeverity>
> <failOnViolation>false</failOnViolation>
> <logViolationsToConsole>true</logViolationsToConsole>
> {code}
> While this achieves the desired effect, it produces a warning:
> {code}
> [WARNING] checkstyle:check violations detected but failOnViolation set to false
> {code}
> Moreover, all found violations, whether errors, warnings, or infos, are logged as {{[ERROR]}}'s on Maven's console. It would be nice if the {{maven-checkstyle-plugin}} would use the corresponding Maven log levels instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira