I agree, you need to first set the tools to look at the worst problems. The idea of using such tools is to find the modules that are most at risk, so you can concentrate extra effort on them. This has worked well for me in the past, but I've never been able to get a whole project using it. I don't intend for you to go in and fix thousands of nit picks.
Ray P.S.: Thanks for the link, I'll check it out. Dimitry Polivaev wrote: > There is a free static code analysis plug-in for eclipse > > http://eclipse-cs.sourceforge.net/ > > The Eclipse Checkstyle plug-in won the Eclipse Community Award 2007 in > the category of "Best Open Source Eclipse-based Developer tool". > > But it has reported so many issues that I have switched it off: there > must be a discussion and decision about how and when to use such tools > before we start using them in project. > > Dimitry > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Freemind-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freemind-developer > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freemind-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
