Hello
I would like to start a discussion about trying to unify which Maven
reports should be used for each commons component. The reasons I find
for unifying the reports are these:
- Makes it easy for our users if we are consistent - they know what to
expect
- Makes it easier for us to maintain our project.xml files
- Facilitate Maven 2 migration
Digging into the Maven 1 POMs for commons proper I have come up with the
list of reports here below. Some reports that are only used in a few
components have been omitted. 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".
+ means that I think that all components should use this report
o means that I think this report should be optional
- means that I don't think any component should use this report
Standard
+ license
Source health
+ checkstyle (code formatting)
+ jdepend (quality metrics)
+ pmd/cpd (bugs, code duplication, coding standards)
+ tasklist (to do list)
- findbugs (same as pmd?)
- simian (same as cpd)
Tests
+ cobertura (test coverage)
+ junit (test reports)
- clover (same as cobertura)
- jcoverage (same as cobertura)
Changes since last release
+ changelog (SCM activity per commit)
+ clirr (binary compatibility)
+ developer-activity (SCM activity per developer)
+ file-activity (SCM activity per file)
o changes
- jdiff (same as clirr)
Reference
+ javadoc
+ jxr (cross reference)
User guide
o faq
- linkcheck (might be enabled during development)
With that I will duck from the flames and see what the rest of you think :)
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
