DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36306>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36306 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-04 16:44 ------- Since most IDEs use Checkstyle behind the scenes, and if they don't they almost all have some sort of plug-in or extension to use it, I would really suggest getting Checkstyle to do what you want. Rememeber that not everyone uses an IDE, crazy as some may say we are because of it :) My opinion at least is that there shouldn't be anything about Struts that requires an IDE, or any particular IDE (or even a group of supported IDEs), and the path your on seems to be going that way. Also, with Java Web Parts as an example, the Checkstyle execution is part of the build script, as it currently is for Struts as well... one of my requirements when cutting a release is that there are no Checkstyle complaints at all. I'm pretty anal about it actually :) I haven't gone so far as to abort the build if any are found, but I could, and probably will at some point. This in essence automates compliance with the rules, to a degree (someone still has to fix things manually of course). I would think the same would be important for Struts... especially if you have an automated build process in place, which I believe there is, right? Obviously that would be bad now because of all the complaints there are, but if you got the code base "clean" as far as Checkstyle goes, from that point on if you got a Gump alert even for a simple Checkstyle failure, that would tend to enforce the rules rather well :) I don't think you could do the same with an IDE-based check. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
