> + checkstyle (code formatting)
> + pmd/cpd (bugs, code duplication, coding standards)
Agree, and think commons should specify common settings for both (the
pmd ones might be harder to agree on though, so might vary).
Uh ...I think checkstyle might be a hard one. And TBH I think that's
not worth the debate. People can be very passioned about this. I also
just hate it to be locked in into some of the styling rules sometimes.
I think checkstyle like it is, is the wrong approach. It would be
really cool to have the code in the scm in a certain style and then
format it on checkout and on back to the standard format on commit.
But I fear that's a pretty wild idea :)
> + jdepend (quality metrics)
Unless you really get what it means and use it, I'd leave it out.
yepp ...leave it out
> + tasklist (to do list)
You may be able to achieve this with checkstyle instead, this one is
really just for convenience.
I prefer the tasklist one
> + clirr (binary compatibility)
You might also look at Torsten's recent work on jardiff for Maven 2.
Unfortunately codehaus was down when I wanted to commit. So it's still
sitting in Jira ..and on my disk
> + developer-activity (SCM activity per developer)
> + file-activity (SCM activity per file)
probably optional
I like the developer-activity one because it shows you the latest
changes. Something like the changelog report but based on the scm
commits.
> - jdiff (same as clirr)
It's actually quite different, but I think it is best used on-demand to
browse the changes rather than as a report like clirr.
Hm.. nevery really used that one when I had clirr/jardiff though.
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
