Built by Maven

changes:changes

Note:

This goal should be used as a Maven report.

Full name:

org.apache.maven.plugins:maven-changes-plugin:3.0.0-M1:changes

Description:

Goal which creates a nicely formatted Changes Report in html format from a changes.xml file.

Attributes:

  • Requires a Maven project to be executed.
  • The goal is thread-safe and supports parallel builds.
  • Since version: 2.0.

Required Parameters

Name Type Since Description
<basedir> String 2.10 The current project base directory.
User Property: basedir
<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
<addActionDate> boolean 2.1 A flag whether the report should also include the dates of individual actions. If set to false, only the dates of releases will be written to the report.
Default: false
User Property: changes.addActionDate
<aggregated> boolean 2.5 A flag whether the report should also include changes from child modules. If set to false, only the changes from current project will be written to the report.
Default: false
<feedType> String 2.9 The type of the feed to generate.

Supported values are: "rss_0.9", "rss_0.91N" (RSS 0.91 Netscape), "rss_0.91U" (RSS 0.91 Userland), "rss_0.92", "rss_0.93", "rss_0.94", "rss_1.0", "rss_2.0", "atom_0.3", "atom_1.0".

If not specified, no feed is generated.

<filteringChanges> boolean 2.2 applying filtering filtering "a la" resources plugin
Default: false
<issueLinkTemplatePerSystem> Map<String,String> 2.1 Template strings per system that is used to discover the URL to use to display an issue report. Each key in this map denotes the (case-insensitive) identifier of the issue tracking system and its value gives the URL template.

There are 2 template tokens you can use. %URL%: this is computed by getting the <issueManagement>/<url> value from the POM, and removing the last '/' and everything that comes after it. %ISSUE%: this is the issue number.

Note: The deprecated issueLinkTemplate will be used for a system called "default".

Note: Starting with version 2.4 you usually don't need to specify this, unless you need to link to an issue management system in your Changes report that isn't supported out of the box. See the Usage page for more information.

<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}
<publishDateFormat> String 2.2 Format to use for publishDate. The value will be available with the following expression ${publishDate}
See also: java.text.SimpleDateFormat
Default: yyyy-MM-dd
<publishDateLocale> String 2.2 Locale to use for publishDate when formatting
See also: java.util.Locale
Default: en
<runOnlyAtExecutionRoot> boolean 2.10 This will cause the execution to be run only at the top of a given module tree. That is, run in the project contained in the same folder where the mvn execution was launched.
Default: false
User Property: changes.runOnlyAtExecutionRoot
<siteDirectory> File - Directory containing the site.xml file.
Default: ${basedir}/src/site
<team> String 2.4 The URI of a file containing all the team members. If this is set to the special value "none", no links will be generated for the team members.
Default: team.html
<xmlPath> File - The path of the changes.xml file that will be converted into an HTML report.
Default: src/changes/changes.xml
User Property: changes.xmlPath

Parameter Details

<addActionDate>

A flag whether the report should also include the dates of individual actions. If set to false, only the dates of releases will be written to the report.
  • Type: boolean
  • Since: 2.1
  • Required: No
  • User Property: changes.addActionDate
  • Default: false

<aggregated>

A flag whether the report should also include changes from child modules. If set to false, only the changes from current project will be written to the report.
  • Type: boolean
  • Since: 2.5
  • Required: No
  • Default: false

<basedir>

The current project base directory.
  • Type: java.lang.String
  • Since: 2.10
  • Required: Yes
  • User Property: basedir

<feedType>

The type of the feed to generate.

Supported values are: "rss_0.9", "rss_0.91N" (RSS 0.91 Netscape), "rss_0.91U" (RSS 0.91 Userland), "rss_0.92", "rss_0.93", "rss_0.94", "rss_1.0", "rss_2.0", "atom_0.3", "atom_1.0".

If not specified, no feed is generated.

  • Type: java.lang.String
  • Since: 2.9
  • Required: No

<filteringChanges>

applying filtering filtering "a la" resources plugin
  • Type: boolean
  • Since: 2.2
  • Required: No
  • Default: false

<issueLinkTemplatePerSystem>

Template strings per system that is used to discover the URL to use to display an issue report. Each key in this map denotes the (case-insensitive) identifier of the issue tracking system and its value gives the URL template.

There are 2 template tokens you can use. %URL%: this is computed by getting the <issueManagement>/<url> value from the POM, and removing the last '/' and everything that comes after it. %ISSUE%: this is the issue number.

Note: The deprecated issueLinkTemplate will be used for a system called "default".

Note: Starting with version 2.4 you usually don't need to specify this, unless you need to link to an issue management system in your Changes report that isn't supported out of the box. See the Usage page for more information.

  • Type: java.util.Map<java.lang.String, java.lang.String>
  • Since: 2.1
  • Required: No

<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}

<publishDateFormat>

Format to use for publishDate. The value will be available with the following expression ${publishDate}
See also: java.text.SimpleDateFormat
  • Type: java.lang.String
  • Since: 2.2
  • Required: No
  • Default: yyyy-MM-dd

<publishDateLocale>

Locale to use for publishDate when formatting
See also: java.util.Locale
  • Type: java.lang.String
  • Since: 2.2
  • Required: No
  • Default: en

<runOnlyAtExecutionRoot>

This will cause the execution to be run only at the top of a given module tree. That is, run in the project contained in the same folder where the mvn execution was launched.
  • Type: boolean
  • Since: 2.10
  • Required: No
  • User Property: changes.runOnlyAtExecutionRoot
  • Default: false

<siteDirectory>

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

<team>

The URI of a file containing all the team members. If this is set to the special value "none", no links will be generated for the team members.
  • Type: java.lang.String
  • Since: 2.4
  • Required: No
  • Default: team.html

<xmlPath>

The path of the changes.xml file that will be converted into an HTML report.
  • Type: java.io.File
  • Required: No
  • User Property: changes.xmlPath
  • Default: src/changes/changes.xml