[ http://jira.codehaus.org/browse/MPCHECKSTYLE-34?page=comments#action_41547 ]
Scott Lamb commented on MPCHECKSTYLE-34: ---------------------------------------- Oh, wow. I can't believe I missed maven.checkstyle.usefile. It works fine. Thanks. > Show errors on maven.checkstyle.fail.on.violation > ------------------------------------------------- > > Key: MPCHECKSTYLE-34 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-34 > Project: maven-checkstyle-plugin > Type: Improvement > Versions: 2.5 > Reporter: Scott Lamb > Priority: Minor > > > I turned on maven.checkstyle.fail.on.violation, so our builds fail on serious > enough errors. It works, but the output is not terribly enlightening: > BUILD FAILED > File...... > /Users/slamb/.maven/cache/maven-checkstyle-plugin-2.5/plugin.jelly > Element... ant:checkstyle > Line...... 144 > Column.... 63 > Got 15 errors. > To actually find what the error was, I have to dig into > build/checkstyle-raw-report.txt. It'd be much more helpful if it actually > send the offending errors to stdout. This would be better because: > - They'd show up in the Cruise Control emails > - I wouldn't have to do a "egrep -v ': (warning|info):' > build/checkstyle-raw-report.txt" to find the errors...checkstyle doesn't even > write "error" on error lines. > - It'd integrate better with editors that grep the build output to take you > to the violation automatically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
