I'll broach the subject with the Checkstyle developers. I asked here first to see if anyone had any dealings in the matter. I wasn't suggesting Maven should solve the hierarchical configuration issue just wondering what people thought of the idea. I'll raise the thread on the Checkstyle list and see what they have to say on the matter.
Thanks for everyone's input.
-John K
On 9 Nov 2003, at 02:48, __matthewHawthorne wrote:
The way I see it, Maven doesn't want to get involved with configuring Checkstyle. It just calls Checkstyle for you with a user provided file, or a default. Adding some heirarchical configuration loader for Checkstyle sounds nice, but then Maven would have to consider doing the same for a lot of other plugins. It seems easiest and most efficient to keep things separate.
However, this may be a nice workaround:
I like the Checkstyle plugin for Eclipse. I believe that the defaults that it uses are based on the Sun standards. You can create a copy of the default, rename it, customize it to your liking, and then export it to an xml file. Perhaps you could then use this file in Maven?
Hope this helps.
John Keyes wrote:Is it possible to override configuration settings in the current Checkstyle plugin like it was possible when properties files were used?
maven.checkstyle.properties=my-checkstyle.xmlYes but I have to specify all of the rules again in that file. I think it should be extensible.Why not? It's bad that it doesn't work as advertised.For example, I would like to use the sun coding standard as the base for my coding standard and I want to change some of the settings.
a) Be warned, the sun_checks.xml do not implement the sun coding standard.b) Have you seen Jalopy? http://jalopy.sourceforge.net/ There is a 'jalopy' goal.Yeah, but it doesn't haven any relevance to this discussion. I just like the idea of being able to import a base standard and customize that as I see fit. -John K
--------------------------------------------------------------------- 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]
