Dennis Lundberg wrote:
I have also tried to categorize and describe each report, borrowing/stealing a lot from chapter 6 in the new book "Better Builds with Maven".
Why would you want to do that? :D
+ 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).
+ jdepend (quality metrics)
Unless you really get what it means and use it, I'd leave it out.
+ tasklist (to do list)
You may be able to achieve this with checkstyle instead, this one is really just for convenience.
+ clirr (binary compatibility)
You might also look at Torsten's recent work on jardiff for Maven 2.
+ developer-activity (SCM activity per developer) + file-activity (SCM activity per file)
probably optional
- 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.
Cheers, Brett -- Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
