Steve Appling wrote:
Adam Murdoch wrote:
Steve Appling wrote:
I had my first encounter with the new checkstyle tasks as part of
making an explodedDist of gradle today. I love having support for
this, but have a couple of thoughts.
Is there an intent to format the checkstyle results into an HTML
report like the codeNarc ones, or is the output always going to be raw?
As a report, I think.
That would be great.
If there is no intent for a formatted report (or until there is
one), can the output be changed to plain text and filtered to only
show violations. It is awkward to have to search through the xml to
find the source of the problem.
The problems are also reported on the console, so you shouldn't need
to look at the report to fix them.
All I get is:
Execution failed for task ':checkstyle'.
Cause: Checkstyle check violations were found in main java source. See
the report at C:\OpenSource\gradle\debug_v2\build\checkstyle\main.xml.
BUILD FAILED
The xml file lists every file that passed as well as the violations, so
it is a little awkward to use. It would be great if just the violations
showed up on the console.
I take that back. Sorry Adam, I missed the message further up the page. You
were correct.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
