Pete, suggestions on how....I'm -1 on this until someone can explain how
we can loop through the <sourceDirectory>'s and run a check style on
each....this is the suggestion, right?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
"Pete Kazmier" <[EMAIL PROTECTED]>
05/26/02 11:23 PM
Please respond to "Turbine Maven Developers List"
To: [EMAIL PROTECTED]
cc:
Subject: Re: several checkstyle reports vs one
+1
Breaking the checkstyle report into many has been something we've wanted
to do for a while. At first, I was not in favor of this because I
thought the errors would quickly disappear and we'd just get stuck with
a lot of empty reports; however, in practice, it seems that the errors
are not going away and as it is now, the report is too big and renders
slowly on many browsers. I think multiple reports would be good.
On Sun, May 26, 2002 at 11:22:16AM +0100, Vincent Massol wrote:
> Shouldn't we have onc checkstyle report per source directory (i.e.
> <sourcedirectory>) rather than everything under src/ in one report ?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
