Andreas Gudian created MCHECKSTYLE-255:
------------------------------------------

             Summary: First checkstyle error is not printed in the console ouput
                 Key: MCHECKSTYLE-255
                 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-255
             Project: Maven Checkstyle Plugin
          Issue Type: Bug
            Reporter: Andreas Gudian


During fixing the checkstyle errors for surefire, I noticed that the very first 
checkstyle error is not printed on the console ouput.

For example, the checkstyle-result.xml contains 111 errors for surefire-common 
(in my local version) and for AbstractSurefireMojo.java, there are two errors 
(file has too many lines, and @Nonnull at the wrong position)

{code}
[INFO] There are 111 checkstyle errors.
[ERROR] AbstractSurefireMojo.java[2296:16] (modifier) ModifierOrder: '@Nonnull' 
Annotation-Modifier sollte vor den anderen Modifie
rn stehen.
[ERROR] BooterSerializer.java[78:114] (whitespace) ParenPad: Vor ')' befindet 
sich kein Leerzeichen.

... nothing more about AbstractSurefireMojo.java

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.825s
[INFO] Finished at: Sat Oct 25 20:26:42 CEST 2014
[INFO] Final Memory: 11M/109M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check (default-cli) on 
project maven-surefire
-common: You have 101 Checkstyle violations. -> [Help 1]
{code}

The summary about the failing build says something about 101 checkstyle 
violations, not 111 errors as above.

I also noticed that if I fix all but one checkstyle error, the module passes 
the test. The output contains just the line "[INFO] There are 1 checkstyle 
errors." for that module and then continues with the next build.



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

Reply via email to