This document provides an overview of the various reports that are automatically generated by Maven . Each report is briefly described below.
| Document | Description |
|---|---|
| Breaking News | The following changes break API or behavior of the previous version. |
| Build Report | Reports about meta data gathered during the build. |
| Change Log | Generated change log report from SCM. |
| Checkstyle | Report on coding style conventions. |
| Clirr | Report on binary and source API differences between releases |
| Cobertura Test Coverage | Cobertura Test Coverage Report. |
| Configuration Properties | Report on configuration properties used in this project. |
| CPD Report | Duplicate code detection. |
| Developer Activity | Generated developer activity report from SCM. |
| File Activity | Generate file activity report from SCM. |
| FindBugs Report | Generates a source code report with the FindBugs Library. |
| Javadoc Messages Report | Report checks that API documentation is complete and free of errors. |
| JavaNCSS Report | Code metric analysis. |
| JDepend | JDepend traverses Java class file directories and generates design quality metrics for each Java package. JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to manage package dependencies effectively. |
| New and Noteworthy | This version presents the following key features. |
| PMD Report | Verification of coding rules. |
| Release Notes | Information about changes provided in this release. |
| Release Plan | Information about planned changes. |
| Surefire Report | Report on the test results of the project. |