Built by Maven

project-info-reports:scm

Note:

This goal should be used as a Maven report.

Full name:

org.apache.maven.plugins:maven-project-info-reports-plugin:3.8.0:scm

Description:

Generates the Project Source Code Management (SCM) report.

Attributes:

  • Requires a Maven project to be executed.
  • The goal is not marked as thread-safe and thus does not support parallel builds.
  • Since version: 2.0.

Required Parameters

Name Type Since Description
<outputDirectory> File - The shared output directory for the report. Note that this parameter is only evaluated if the goal is run directly from the command line. If the goal is run indirectly as part of a site generation, the shared output directory configured in the Maven Site Plugin is used instead.

A plugin may use any subdirectory structure (either using a hard-coded name or, ideally, an additional user-defined mojo parameter with a default value) to generate multi-page reports or external reports with the main output file (entry point) denoted by #getOutputName().


Default: ${project.build.directory}/reports

Optional Parameters

Name Type Since Description
<anonymousConnection> String 2.1 The SCM anonymous connection url respecting the SCM URL Format.
See also: SCM URL Format
Default: ${project.scm.connection}
<checkoutDirectoryName> String - The directory name to checkout right after the SCM URL.
Default: ${project.artifactId}
<customBundle> String 2.3 Path for a custom bundle instead of using the default one.
Using this field, you could change the texts in the generated reports.
Default: ${project.basedir}/src/site/custom/project-info-reports.properties
<developerConnection> String 2.1 The SCM developer connection url respecting the SCM URL Format.
See also: SCM URL Format
Default: ${project.scm.developerConnection}
<licenseMappings> List<LicenseMapping> 3.3.1 A mapping of license names to group licenses referred to with different names together
<locale> String - The locale to use when the report generation is invoked directly as a standalone Mojo.
See also: SiteTool#DEFAULT_LOCALE, SiteTool#getSiteLocales(String)
Default: default
<outputFormat> String - The report output format: null by default, to represent a site, but can be configured to a Doxia Sink id.
User Property: output.format
<outputTimestamp> String - Timestamp for reproducible output archive entries, either formatted as ISO 8601 yyyy-MM-dd'T'HH:mm:ssXXX or as an int representing seconds since the epoch (like SOURCE_DATE_EPOCH).
Default: ${project.build.outputTimestamp}
<scmTag> String 2.8 The SCM tag.
Default: ${project.scm.tag}
<siteDirectory> File - Directory containing the site.xml file.
Default: ${basedir}/src/site
<skip> boolean 2.8 Skip report.
Default: false
User Property: mpir.skip
<skipEmptyReport> boolean 2.8 Skip the project info report generation if a report-specific section of the POM is empty. Defaults to true.
Default: true
<webAccessUrl> String 2.1 The SCM web access url.
Default: ${project.scm.url}

Parameter Details

<anonymousConnection>

The SCM anonymous connection url respecting the SCM URL Format.
See also: SCM URL Format
  • Type: java.lang.String
  • Since: 2.1
  • Required: No
  • Default: ${project.scm.connection}

<checkoutDirectoryName>

The directory name to checkout right after the SCM URL.
  • Type: java.lang.String
  • Required: No
  • Default: ${project.artifactId}

<customBundle>

Path for a custom bundle instead of using the default one.
Using this field, you could change the texts in the generated reports.
  • Type: java.lang.String
  • Since: 2.3
  • Required: No
  • Default: ${project.basedir}/src/site/custom/project-info-reports.properties

<developerConnection>

The SCM developer connection url respecting the SCM URL Format.
See also: SCM URL Format
  • Type: java.lang.String
  • Since: 2.1
  • Required: No
  • Default: ${project.scm.developerConnection}

<licenseMappings>

A mapping of license names to group licenses referred to with different names together

<locale>

The locale to use when the report generation is invoked directly as a standalone Mojo.
See also: SiteTool#DEFAULT_LOCALE, SiteTool#getSiteLocales(String)
  • Type: java.lang.String
  • Required: No
  • Default: default

<outputDirectory>

The shared output directory for the report. Note that this parameter is only evaluated if the goal is run directly from the command line. If the goal is run indirectly as part of a site generation, the shared output directory configured in the Maven Site Plugin is used instead.

A plugin may use any subdirectory structure (either using a hard-coded name or, ideally, an additional user-defined mojo parameter with a default value) to generate multi-page reports or external reports with the main output file (entry point) denoted by #getOutputName().

  • Type: java.io.File
  • Required: Yes
  • Default: ${project.build.directory}/reports

<outputFormat>

The report output format: null by default, to represent a site, but can be configured to a Doxia Sink id.
  • Type: java.lang.String
  • Required: No
  • User Property: output.format

<outputTimestamp>

Timestamp for reproducible output archive entries, either formatted as ISO 8601 yyyy-MM-dd'T'HH:mm:ssXXX or as an int representing seconds since the epoch (like SOURCE_DATE_EPOCH).
  • Type: java.lang.String
  • Required: No
  • Default: ${project.build.outputTimestamp}

<scmTag>

The SCM tag.
  • Type: java.lang.String
  • Since: 2.8
  • Required: No
  • Default: ${project.scm.tag}

<siteDirectory>

Directory containing the site.xml file.
  • Type: java.io.File
  • Required: No
  • Default: ${basedir}/src/site

<skip>

Skip report.
  • Type: boolean
  • Since: 2.8
  • Required: No
  • User Property: mpir.skip
  • Default: false

<skipEmptyReport>

Skip the project info report generation if a report-specific section of the POM is empty. Defaults to true.
  • Type: boolean
  • Since: 2.8
  • Required: No
  • Default: true

<webAccessUrl>

The SCM web access url.
  • Type: java.lang.String
  • Since: 2.1
  • Required: No
  • Default: ${project.scm.url}