Simplest way round it would be to use a custom checkstyle file for the
project, then you have complete control over the contents.
In Struts, we have a custom file at /conf/qa/CheckStyle.xml . You tell
Maven which file to use by adding a line to the project.properties
file -
maven.checkstyle.properties = conf/qa/CheckStyle.xml
If you want to go hunting for what changed to cause the problem, start
by looking in your .maven/plugins directory (e.g. (mine is at
D:\Development\.maven\plugins\maven-checkstyle-plugin-2.1\plugin-resourc
es), which is where the default files are stored.
You could also check the CVS for the checkstyle plugin project to see if
the Turbine file has actually changed.
Steve
> -----Original Message-----
> From: Martin Cooper [mailto:[EMAIL PROTECTED]
> Sent: March 10, 2004 7:23 PM
> To: [EMAIL PROTECTED]
> Subject: [all] Maven Checkstyle rules
>
>
> Actually, I'm not sure how many components this applies to...
>
> FileUpload used to pass Checkstyle with no complaints (except for CVS
> keyword lines too long). Now there are hundreds of errors:
>
> http://jakarta.apache.org/commons/fileupload/checkstyle-report.html
>
> Does anyone have any idea what happened? The errors seem to
> imply that the
> definition of the rules (in this case, Turbine rules) changed
> somewhere
> along the line, and there are new rules for all sorts of things.
>
> Anyone know how I can go back to using the old rules, rather
> than having
> to fix a couple of hundred Checkstyle complaints?
>
> TIA.
>
> --
> Martin Cooper
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
