|  | 
                            
                  
    
    
        This document provides an overview of the various reports that
        are automatically generated by 
        Maven
.
        Each report is briefly described below.
       
    
      
            
        | Document | Description |   
        | Changes | This document provides a history of the changes made to the
              project, in a user friendly format, generated from the
              xdocs/changes.xml file. |  
        | Change Log | This document provides a history of the most recent
              changes made to the project taken directly from the
              source code repository. |   
        | Developer Activity | This document provides a report of activity in terms of
              CVS commits and breaks it out by developer. |  
        | File Activity | This document provides a report of activity in terms of
              CVS commits and breaks it out by file. |   
        | Tasks | This document provides a list of tasks that need to
              be completed for the project, generated from the
              xdocs/tasks.xml file. |  
        | Task List | This document provides a list of tasks that need to
              be completed for the project, generated from the
              @task javadoc tag in java source code. |   
        | Unit Tests | This document provides the results of the unit tests that
              are part of this project.  Successes and failures are
              noted. |  
        | Metric Results | This document provides information on various source code
              metrics that have been computed.  These metrics can
              provide useful information regarding the abstractness and
              total number of classes. |   
        | Checkstyle Report | This document provides the results of the Checkstyle
              report.  This report provides an indication of how well
              this project complies with its coding conventions. |  
        | Javadoc Report | This document the details of javadoc execution against
              the project. This encourages the reduction of javadoc
              errors. |  |