Thanks, Tom. That narrowed down the search to 1 in 500 lines, plus it
gave me hope I was looking in the right place. I did not expect that
checkstyle would be so user-unfriendly to mix together important error
information with large amounts of routine "file foo checked out okay".
Anyone who has an account at jira.codhaus.org, please vote this up:
http://jira.codehaus.org/browse/MCHECKSTYLE-51
an unassigned, 6+ year old request to improve checkstyle reporting.
Notes on checkstyle, for the record:
Adding
-Dmaven.checkstyle.fail.on.violation=true
-Dmaven.checkstyle.usefile=false
to the mvn command line did not result in the checkstyle error being
displayed in stdout/stderr.
Paul
On 20130313 6:55 , Tom White wrote:
I usually look in the checkstyle-result.xml file for the module that
failed. It contains the error message in a fairly readable form.
Tom
On Tue, Mar 12, 2013 at 4:32 AM, Paul Baclace <[email protected]> wrote:
I'm building Whirr and see a checkstyle error, but the specific problem is
not presented in an easy to digest fashion, and 11,000 lines of checkstyle
output files is a bit much to sift through without knowing what to look for.
Clues?
Paul
