commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Caswell <>
Subject Re: [lang] checkstyle report
Date Wed, 25 May 2005 21:10:44 GMT
I propose that for the upcoming lang 2.1 release we leave the errors unfixed 
and leave the checkstyle report as is.

1. Leave them unfixed because the errors are all documentation-related, and 
while it is important to fix them, I don't believe the problems are 
detrimental to the product. It has taken long enough to get the release out 
(and I take some of the blame for the slowness) and I don't believe it is 
worth delaying longer to make what I consider marginally useful fixes. 
Unless someone gets to them before the final RC.

2. Leave the checkstyle report as is because the problems should be fixed, 
and I'm worried that if we hide them for this release then they'll be 
forgotten. I'd rather take the time after the release to either fix them or 
hide them after appropriate discussion, which I believe should also not hold 
up the release.


On 5/24/05, Simon Kitching <> wrote:
> Hi,
> I've checked
> and there is a massive number of checkstyle errors reported.
> I suggest you either fix them or turn off the checkstyle checks you
> don't want. Fixing the problem is probably better.
> By the way, I've struck a checkstyle problem when using it in the
> digester site. Despite having
> it doesn't look to me like the specified checkstyle.xml file is actually
> being used. I can even change the contents to invalid xml and no error
> is reported.
> Lang has exactly the same setup for checkstyle reports. Does the
> checkstyle.xml file have any effect in lang?
> Regards,
> Simon
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Steven Caswell

Take back the web -

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message