|target/||Contains compiled classes and JARs.||
The contents of the target/ directory should be enough to use the project. This directory
contains the final JAR and WAR that are generated.
|target/classes||Contains compiled classes.||
The target/classes directory contains all compiled classes. This directory is used when
packaging the final JAR for a project.
|target/generated-docs||Contains Maven generated xdocs.||
The target/generated-docs directory contains all of the Maven-generated xdocs. All content
generated by Maven is first converted to xdoc format, so the same stylesheet used to transform
the rest of the site can be used on generated content. The contents of this directory are
transformed and stored in the docs/ directory.
|target/docs||Documentation files intended for the website publication.||
The docs/ directory contains only generated documentation that is intended to be published as
the project's website. This directory includes the Velocity/DVSL generated HTML files,
JavaDocs, cross-referenced sources, and various generated reports. Generally, all documentation
is stored in the xdocs/ directory and then "transformed" into this directory. The specific
documents that Maven generates are described below.
|target/docs/index.html||Starting point for browsing the documentation.||
Browsing the documentation locally should yield the same results as browsing the documentation
on the project's home page.
Maven automatically generates JavaDocs for projects using the JavaDoc utility. Placing the API
documentation under docs/apidocs/ makes it slightly easier for other documentation files under
docs/ to reference API documentation and vice versa.
|target/docs/xref||Cross-referenced source code.||
Maven automatically generates cross-referenced source code that enables easy browsing of an
entire source tree. Placing the cross-referenced sources under docs/xref/ makes it slightly
easier for other documentation files under docs/ to reference API documentation and vice versa.
|target/docs/mail-lists.html||Mailing list documentation.||
Maven automatically generates a list of mailing lists based on the information provided in the
|target/docs/team-list.html||The list of project team members.||
Maven automatically generates a list of project team members based on the information provided
in the project descriptor.
|target/docs/dependencies.html||The list of dependencies.||
Maven automatically generates a list of dependencies based on the information provided in the
|target/docs/changelog.html||The CVS change log.||
Maven automatically generates a change log from CVS log messages. This log is currently limited
to the past 30 days (but will be configurable in the future).
|target/docs/file-activity-report.html||The File Activity Report.||
Maven automatically generates a log from your SCM listing file changes in the last 30 days.
|target/docs/developer-activity-report.html||The Developer Activity Report.||
Maven automatically generates a log from your SCM listing changes per developer in the last 30
Maven automatically generates a report on various source code metrics. This report can provide
further insight into a project.
Maven automatically generates a report on the results of Checkstyle. This report provides
assurance that the coding conventions for your project are being followed.