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-sensitive) 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".

Report output directory. Note that this parameter is only relevant
if the goal is run from the command line or from the default build
lifecycle. If the goal is run indirectly as part of a site
generation, the output directory configured in the Maven Site
Plugin is used instead.Default value is: ${project.reporting.outputDirectory}.

Deprecated. As of 2.1 use issueLinkTemplatePerSystem : this one will be with
system default

Template string that is used to discover the URL to use to display
an issue report. 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: In versions of this plugin prior to
2.0-beta-2 this parameter was called
link_template.

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-sensitive) 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".

Report output directory. Note that this parameter is only relevant
if the goal is run from the command line or from the default build
lifecycle. If the goal is run indirectly as part of a site
generation, the output directory configured in the Maven Site
Plugin is used instead.