Yes but I have to specify all of the rules again in that file. I think it should be extensible.
I don't see why. Its a configuration file. Create your own configuration. It is just as easy to copy the file and edit it.
Of course you can. I just think its a step backwards in comparison to the previous version.
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.
Why not? It's bad that it doesn't work as advertised.
Read the Sun coding standards. They don't AvoidInlineConditionals, for example. The Sun coding standard says nothing about DesignForExtension, since design is not an aspect of formatting. Correct your RedundantThrows and then there is no way to javadoc a method that might throw both an IOException and a FileNotFoundException. Loath FinalParameters.
Well then the file should not be called sun_checks.xml, it is just another user configuration. The sun coding standard support should do exactly what it says on the tin and nothing more.
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.
It is relevent. With Jalopy your code will comply to the Sun coding standards. Is that now what you want?
"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."
I know how to resolve the issue, I am just highlighting an area of weakness (IMO) with the current version.
Cheers, -John K
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
