[
https://jira.codehaus.org/browse/MCHECKSTYLE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHECKSTYLE-182.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.12
Assignee: Dennis Lundberg
Patch applied with modifications in
[r1570746|http://svn.apache.org/viewvc?view=revision&revision=1570746]. Many
thanks!
> Use Maven log levels when logging to console
> --------------------------------------------
>
> Key: MCHECKSTYLE-182
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-182
> Project: Maven Checkstyle Plugin
> Issue Type: Improvement
> Affects Versions: 2.9.1
> Reporter: Andreas Sewe
> Assignee: Dennis Lundberg
> Priority: Minor
> Fix For: 2.12
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
