Menu
▾
▴
#124 over time, show more errors
We set all our checkstyle rules to errors. warnings have been useless on the past 3 teams as no one fixes warnings. The deal with errors though is they can be overwhelming. In our build.xml file, for legacy systems, we allow a max errors number. we would love to specify a max errors for the checkstyle eclipse plugin and the plugin only shows RANDOMLY errors above the max. ie. If max errors is 800 and there is 820 errors, the plugin will only show 20 errors.
Then the next step which helps ALOT is to specify how much to reduce the max errors over time so that every week, max errors goes from 800 to 795 to 790, etc. etc.
hardly anyone fixes warnings...errors is the only way to get noticed (and our setup of checkstyle breaks the build and forces people to fix them). Just hoping we can add a time variant here as our system seems to stay at 800 errors exactly.
Moving to feature requests.
I feel this request pretty much out of scope of the eclipse-cs plugin, since it is a tool FOR developers WANTING to improve their code.
If developers don't share this mindset (which is sadly often the case) or don't get time assigned by management to fix warnings (which is sadly even more often the case) then the eclipse-cs tool can't be of much help.
Maybe it is in your case more gainful to track progression of Checkstyle warnings over time using a Continuous Integration Server (for example Hudson) which is able to do just that.
If a project shows no progress over time then you still can get the prod out...
You're likely better suited with tools like Sonar for this particular use case.
Closing as part of housekeeping.