[ 
https://jira.codehaus.org/browse/MCHECKSTYLE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355221#comment-355221
 ] 

Herve Boutemy edited comment on MCHECKSTYLE-243 at 10/30/14 3:51 AM:
---------------------------------------------------------------------

you(re not looking at what was done in this Jira issue, ie 
[r1614202|http://svn.apache.org/r1614202]: CheckstyleViolationCheckMojo.java 
has been modified = checkstyle:check

nothing has been changed for checkstyle:checkstyle = the report you're showing

and notice that the report you're showing only displays the violation count, 
not the violations themselves = what I'm trying to explain = the 
checkstyle:checkstyle report has not changed, only the heckstyle:check mojo


try {{mvn checkstyle:check}} and you'll see what this Jira issue is about (ie 
not {{mvn site}})


was (Author: hboutemy):
you(re not looking at what was done in this Jira issue, ie 
[r1614202|http://svn.apache.org/r1614202]: CheckstyleViolationCheckMojo.java 
has been modified = checkstyle:check

nothing has been changed for checkstyle:checkstyle = the report you're showing

and notice that the report you're showing only displays the violation count, 
not the violations themselves = what I'm trying to explain = the 
checkstyle:checkstyle report has not changed, only the heckstyle:check mojo


try {{mvn checkstyle:check}} and you'll see what this Jira issue is about (ie 
not {{ mvn site}})

> log check violations to console by default
> ------------------------------------------
>
>                 Key: MCHECKSTYLE-243
>                 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-243
>             Project: Maven Checkstyle Plugin
>          Issue Type: Wish
>          Components: checkstyle:check
>    Affects Versions: 2.12.1
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>             Fix For: 2.13
>
>
> this is useful by default, not only the violation count



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to