I find checkstyle to be not very useful. It's more hassle than it's worth. It's like pointing fingers instead of helping. If you want to foster a certain code style provide eclipse and intellij formatter settings instead - that's actually helping. Especially if you run them before a release.
The basic code style is like logging - people spent just wait too much time on this. Thinks we really should care about are in the findbugs and PMD report. I don't see why we should make checkstyle part of the projects by default. My 2 cents, Torsten On Tue, Mar 13, 2012 at 1:14 PM, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi Torsten! > >> -1 for checkstyle > > With my +1 I meant that, as we discussed in another thread, the parent > could provide a default - but overridable - configuration; I think > that having at least one metric of code style measure in each > component would be nice to have, so unless other preferences, the > parent "suggests" a default config > > I would like to understand better your PoV (that would influence > mine): which are your concerns about having the checkstyle? > > many thanks in advance, all the best, > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
