Greg, I think I don't go about a general clean-up per se. My rule of thumb: if I am working on a feature/bug, I'll be touching files. As I touch them, I checkstyle them. And don't forget about the checkstyle integration within Eclipse.
Werner -----Ursprüngliche Nachricht----- Von: Gregory Block [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 03. August 2005 10:14 An: dev@castor.codehaus.org Betreff: [castor-dev] Checkstyle, and existing source bases.... ... oh my god... Ok, so I've never seen checkstyle before; went and ran it against my codebase. So how do you go about 'cleaning up' ~600 files worth of hundreds of screenfuls of errors??? What do you do for a 'first pass' cleaning run to get rid of tabbing and formatting errors? There's got to be some kind of tool that can get rid of the majority of the crap. What did Castor use when it implemented checkstyle? Elbow grease? ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] ------------------------------------------------- ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
