Author: hboutemy
Date: Sun May 15 18:13:32 2016
New Revision: 1743942
URL: http://svn.apache.org/viewvc?rev=1743942&view=rev
Log:
updated Jira url
Modified:
maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/single/including-and-excluding-artifacts.apt
maven/plugins/trunk/maven-changes-plugin/src/site/apt/usage.apt.vm
maven/plugins/trunk/maven-changes-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm
maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/examples/specifying-source-path-inclusions-and-exclusions.apt.vm
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/reactor.apt
maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt.vm
maven/plugins/trunk/maven-gpg-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-help-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-jarsigner-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/fix-javadocs.apt.vm
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/javadoc-nofork.apt.vm
maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-pdf-plugin/src/site/xdoc/examples/configuring-reports.xml.vm
maven/plugins/trunk/maven-project-info-reports-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-remote-resources-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/index.apt.vm
maven/plugins/trunk/maven-site-plugin/src/site/apt/maven-3.apt.vm
maven/plugins/trunk/maven-site-plugin/src/site/fml/faq.fml
Modified:
maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/single/including-and-excluding-artifacts.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/single/including-and-excluding-artifacts.apt?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
---
maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/single/including-and-excluding-artifacts.apt
(original)
+++
maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/single/including-and-excluding-artifacts.apt
Sun May 15 18:13:32 2016
@@ -75,7 +75,7 @@ Including and Excluding Artifacts
* What about your Project's Artifacts?
- {{{http://jira.codehaus.org/browse/MASSEMBLY-197}MASSEMBLY-197}} added
<<<useProjectArtifact>>>
+ {{{https://issues.apache.org/jira/browse/MASSEMBLY-197}MASSEMBLY-197}} added
<<<useProjectArtifact>>>
and <<<useProjectAttachments>>> to the <<<dependencySet>>> configuration.
See {{{../../assembly.html#class_dependencySet}Assembly Descriptor Format}}
for the default values and how to configure them.
\ No newline at end of file
Modified: maven/plugins/trunk/maven-changes-plugin/src/site/apt/usage.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-changes-plugin/src/site/apt/usage.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-changes-plugin/src/site/apt/usage.apt.vm
(original)
+++ maven/plugins/trunk/maven-changes-plugin/src/site/apt/usage.apt.vm Sun May
15 18:13:32 2016
@@ -194,7 +194,7 @@ mvn site
...
<issueManagement>
<system>JIRA</system>
- <url>http://jira.codehaus.org/browse/MCHANGES</url>
+ <url>https://issues.apache.org/jira/browse/MCHANGES</url>
</issueManagement>
...
</project>
Modified: maven/plugins/trunk/maven-changes-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-changes-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-changes-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-changes-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -59,7 +59,7 @@ mvn -DentityExpansionLimit=128000 ...
<p>
Unfortunately we have not been able to set this in Java. If someone
knows how to do this, then please reopen
- <a href="http://jira.codehaus.org/browse/MCHANGES-75";>MCHANGES-75</a>,
+ <a
href="https://issues.apache.org/jira/browse/MCHANGES-75";>MCHANGES-75</a>,
and tell us how. It would be nicer if this could be set using a
parameter in the POM.
</p>
Modified: maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm
(original)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt.vm Sun
May 15 18:13:32 2016
@@ -597,7 +597,7 @@ mvn dependency:analyze
* The <<<dependency:analyze-dep-mgt>>> mojo
This mojo looks at the dependencies after final resolution and looks for
mismatches in your dependencyManagement section.
- In versions of maven prior to 2.0.6, it was possible to inherit versions
that didn't match your dependencyManagement. See
{{{http://jira.codehaus.org/browse/MNG-1577}MNG-1577}} for more info.
+ In versions of maven prior to 2.0.6, it was possible to inherit versions
that didn't match your dependencyManagement. See
{{{https://issues.apache.org/jira/browse/MNG-1577}MNG-1577}} for more info.
If this mojo detects issues, you should attempt to resolve the discrepancies
before upgrading to 2.0.6 to avoid any surprises. This can be done by upgrading
or downgrading the version in dependencyManagement to match what is actually
being included at runtime, or you can specify a dependency in your project
to override what is being included. You can check the results by rerunning this
mojo.
Modified: maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -61,7 +61,7 @@ under the License.
<faq id="question">
<question>Why is Maven resolving "dependency:xxx" to the older
org.codehaus.mojo:dependency-maven-plugin?</question>
<answer><p>
- Due to a bug in Maven in versions prior to 2.0.7 (<a
href="http://jira.codehaus.org/browse/MNG-2926";>MNG-2926</a>), the search order
was reversed and caused Mojo plugins to supercede ones with the same prefix at
Apache.
+ Due to a bug in Maven in versions prior to 2.0.7 (<a
href="https://issues.apache.org/jira/browse/MNG-2926";>MNG-2926</a>), the search
order was reversed and caused Mojo plugins to supercede ones with the same
prefix at Apache.
The metadata at Mojo was cleaned up when the maven-dependency-plugin
was released at Apache. If you are still experiencing this error, chances are
you have
old metadata in your local repository or in a proxy / internal
repository. Removing <code>/org/codehaus/mojo/maven-metadata.*</code> from your
repo/proxy will cause it to
be refreshed. Alternatively, you can specify the groupId explicitely
in your pom (if you are using a bound goal), or on the command line, use
groupId:artifactId:version:mojo, ie
Modified:
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/examples/specifying-source-path-inclusions-and-exclusions.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/examples/specifying-source-path-inclusions-and-exclusions.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
---
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/examples/specifying-source-path-inclusions-and-exclusions.apt.vm
(original)
+++
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/examples/specifying-source-path-inclusions-and-exclusions.apt.vm
Sun May 15 18:13:32 2016
@@ -25,13 +25,13 @@
Overview
- With the change done as part of
{{{http://jira.codehaus.org/browse/MECLIPSE-443}MECLIPSE-443 "Only include
**/*.java in Java source directories"}}
+ With the change done as part of
{{{https://issues.apache.org/jira/browse/MECLIPSE-443}MECLIPSE-443 "Only
include **/*.java in Java source directories"}}
the .classpath entries for classpathentry kind="src" now specify an
<<<including>>> attribute with a value of <<<"**/*.java">>>.
Previously this attribute was not specified which meant that
eclipse would include any file in this src directory as being on the classpath
and hence compiled.
- This broke Ajdt support as <<<"**/*.aj">>> files were no longer
included on the classpath and
{{{http://jira.codehaus.org/browse/MECLIPSE-538}MECLIPSE-538}} fixed this.
+ This broke Ajdt support as <<<"**/*.aj">>> files were no longer
included on the classpath and
{{{https://issues.apache.org/jira/browse/MECLIPSE-538}MECLIPSE-538}} fixed this.
- {{{http://jira.codehaus.org/browse/MECLIPSE-104}MECLIPSE-104 "Add the
ability to specify source inclusions/exclusions"}} was added put back this
flexibility.
+ {{{https://issues.apache.org/jira/browse/MECLIPSE-104}MECLIPSE-104 "Add
the ability to specify source inclusions/exclusions"}} was added put back this
flexibility.
In summary:
Modified: maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/reactor.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/reactor.apt?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/reactor.apt (original)
+++ maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/reactor.apt Sun May
15 18:13:32 2016
@@ -176,4 +176,4 @@ target
[]
<<Issue:>> The Maven Release Plugin does not support the flat structure
-({{{http://jira.codehaus.org/browse/MRELEASE-261}MRELEASE-261}}).
+({{{https://issues.apache.org/jira/browse/MRELEASE-261}MRELEASE-261}}).
Modified: maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt.vm (original)
+++ maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt.vm Sun May 15
18:13:32 2016
@@ -76,7 +76,7 @@ mvn release:perform -Darguments=-Dgpg.pa
+----------+
This accounts for the fact, that the Release Plugin forks Maven and system
properties of the current Maven session are
- unfortunately not automatically propagated to the forked Maven session (see
also {{{http://jira.codehaus.org/browse/MGPG-9}MGPG-9}}).
+ unfortunately not automatically propagated to the forked Maven session (see
also {{{https://issues.apache.org/jira/browse/MGPG-9}MGPG-9}}).
* Configure passphrase in settings.xml
Modified: maven/plugins/trunk/maven-gpg-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-gpg-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-gpg-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -39,7 +39,7 @@ under the License.
The <code>site.xml</code> that can be deployed alongside parent POMs
was originally attached to the project in such a
way that the GPG Plugin could not get hold of it. To enable signing
of the site descriptor, you need to update to
Maven Site Plugin 2.1.1+ which contains the required fix (see also
- <a href="http://jira.codehaus.org/browse/MSITE-478";>MSITE-478</a>).
+ <a
href="https://issues.apache.org/jira/browse/MSITE-478";>MSITE-478</a>).
</p>
</answer>
</faq>
Modified: maven/plugins/trunk/maven-help-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-help-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-help-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-help-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -37,7 +37,7 @@ under the License.
<question>Why <code>mvn help:active-profiles</code> won't show the
active profiles under Maven 2.1?</question>
<answer>
<p>
- See <a href="http://jira.codehaus.org/browse/MPH-38";>MPH-38</a> for
more info.
+ See <a
href="https://issues.apache.org/jira/browse/MPH-38";>MPH-38</a> for more info.
</p>
</answer>
</faq>
Modified: maven/plugins/trunk/maven-jarsigner-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-jarsigner-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-jarsigner-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-jarsigner-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -64,7 +64,7 @@ under the License.
To fix the problem, just move the assembly execution so it comes
<strong>after</strong> the jarsigner execution in the pom.
</p>
<p>
- The whole story of the problem can be found in <a
href="http://jira.codehaus.org/browse/MJARSIGNER-13";>MJARSIGNER-13</a> issue.
+ The whole story of the problem can be found in <a
href="https://issues.apache.org/jira/browse/MJARSIGNER-13";>MJARSIGNER-13</a>
issue.
</p>
</answer>
</faq>
Modified:
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/fix-javadocs.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/fix-javadocs.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
---
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/fix-javadocs.apt.vm
(original)
+++
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/fix-javadocs.apt.vm
Sun May 15 18:13:32 2016
@@ -60,7 +60,7 @@ Fixing Javadoc Comments
** Current limitations
The <fix> and <test-fix> goals use intensively
{{{http://qdox.codehaus.org/}Qdox}} to extract class/interface/method
- Javadoc from source files. Unfortunately, Qdox has
{{{http://jira.codehaus.org/browse/QDOX}some known issues}}.
+ Javadoc from source files. Unfortunately, Qdox has
{{{https://issues.apache.org/jira/browse/QDOX}some known issues}}.
* Example Call
Modified:
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/javadoc-nofork.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/javadoc-nofork.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
---
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/javadoc-nofork.apt.vm
(original)
+++
maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/javadoc-nofork.apt.vm
Sun May 15 18:13:32 2016
@@ -38,7 +38,7 @@ Generate Javadoc without duplicate execu
stuff like <<<enforcer>>> or generating stubs from a WDSL will be invoked
again, which may lead
to longer build times.
- * See {{{https://jira.codehaus.org/browse/MJAVADOC-369}MJAVADOC-369}} as well.
+ * See {{{https://issues.apache.org/jira/browse/MJAVADOC-369}MJAVADOC-369}} as
well.
* As of version 2.10 two new reports are defined, <<<javadoc-no-fork>>> and
<<<test-javadoc-no-fork>>>
which will not trigger above phases a second time.
Modified: maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -448,7 +448,7 @@ mvn deploy:deploy-file \
<p>
Due to <a href="https://bugs.openjdk.java.net/browse/JDK-8040771";>a
bug in JDK 8</a>
you need at least Java 8u20 for this to work. See
- <a
href="http://jira.codehaus.org/browse/MJAVADOC-393";>MJAVADOC-393</a>
+ <a
href="https://issues.apache.org/jira/browse/MJAVADOC-393";>MJAVADOC-393</a>
for more info.
</p>
</answer>
Modified:
maven/plugins/trunk/maven-pdf-plugin/src/site/xdoc/examples/configuring-reports.xml.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-pdf-plugin/src/site/xdoc/examples/configuring-reports.xml.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
---
maven/plugins/trunk/maven-pdf-plugin/src/site/xdoc/examples/configuring-reports.xml.vm
(original)
+++
maven/plugins/trunk/maven-pdf-plugin/src/site/xdoc/examples/configuring-reports.xml.vm
Sun May 15 18:13:32 2016
@@ -33,7 +33,7 @@ under the License.
<p>
<strong>Note for Maven 3 users</strong>: due to the changes in the
reporting API,
report inclusion does <strong>not</strong> work with Maven 3.
- See <a href="http://jira.codehaus.org/browse/MPDF-41";>MPDF-41</a>.
+ See <a
href="https://issues.apache.org/jira/browse/MPDF-41";>MPDF-41</a>.
</p>
<p>
Since version 1.1, all Maven reports will be included by default in
the generated PDF.
Modified:
maven/plugins/trunk/maven-project-info-reports-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-project-info-reports-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-project-info-reports-plugin/src/site/fml/faq.fml
(original)
+++ maven/plugins/trunk/maven-project-info-reports-plugin/src/site/fml/faq.fml
Sun May 15 18:13:32 2016
@@ -25,7 +25,7 @@ under the License.
<question>Is it possible to customize the labels of the Project Reports
Menu?</question>
<answer>
<p>
- Not yet. See the related issue: <a
href="http://jira.codehaus.org/browse/MPIR-35";>MPIR-35</a>
+ Not yet. See the related issue: <a
href="https://issues.apache.org/jira/browse/MPIR-35";>MPIR-35</a>
</p>
</answer>
</faq>
Modified: maven/plugins/trunk/maven-remote-resources-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-remote-resources-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-remote-resources-plugin/src/site/fml/faq.fml
(original)
+++ maven/plugins/trunk/maven-remote-resources-plugin/src/site/fml/faq.fml Sun
May 15 18:13:32 2016
@@ -48,7 +48,7 @@ under the License.
<li>
File bugs with the projects that produced those artifacts to get
them to fix them. Also,
file bugs with the
- <a href="http://jira.codehaus.org/browse/MEV";>Maven Evangelism</a>
+ <a href="https://issues.apache.org/jira/browse/MEV";>Maven
Evangelism</a>
project to have the Maven people enhance the metadata in the
repository.
</li>
<li>
Modified: maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/index.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/index.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/index.apt.vm
(original)
+++ maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/index.apt.vm Sun
May 15 18:13:32 2016
@@ -34,7 +34,7 @@ ${project.name}
to publish Maven websites via the ASF svnpubsub system.
In addition to SCM operations, it takes care to fix newline inconsistencies
- generated by <<<maven-site-plugin>>> (see
{{{https://jira.codehaus.org/browse/MSITE-121}MSITE-121}}),
+ generated by <<<maven-site-plugin>>> (see
{{{https://issues.apache.org/jira/browse/MSITE-121}MSITE-121}}),
which prevents simple content import to SCM.
The plugin has been tested with git scm too and by example can push
content for github pages.
@@ -100,7 +100,7 @@ mvn scm-publish:publish-scm -Dscmpublish
To reach such a dream, there are some steps:
* fix inconsistent newlines generated by <<<maven-site-plugin>>> (caused
by <<<site.vm>>> template and
- resources taken from skin jar without fixing newlines):
{{{https://jira.codehaus.org/browse/MSITE-121}MSITE-121}}
+ resources taken from skin jar without fixing newlines):
{{{https://issues.apache.org/jira/browse/MSITE-121}MSITE-121}}
is fixed in (future) maven-site-plugin 3.4,
* improve {{{/wagon/wagon-providers/wagon-scm/}<<<wagon-scm>>>}} to put a
whole directory content
Modified: maven/plugins/trunk/maven-site-plugin/src/site/apt/maven-3.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/maven-3.apt.vm?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-site-plugin/src/site/apt/maven-3.apt.vm (original)
+++ maven/plugins/trunk/maven-site-plugin/src/site/apt/maven-3.apt.vm Sun May
15 18:13:32 2016
@@ -32,7 +32,7 @@ Using maven-site-plugin with Maven 3
A major aim of the refactoring in Maven 3 was to decouple the Maven core
from {{{/doxia/}Doxia}}
and to allow arbitrary reporting systems to be developed. For this reason,
all reporting
related code has been removed from the core of Maven 3
- ({{{http://jira.codehaus.org/browse/MNG-4162}MNG-4162}}).
+ ({{{https://issues.apache.org/jira/browse/MNG-4162}MNG-4162}}).
As a result, the 2.x versions of the Maven Site Plugin will not work with
Maven 3.
Using such versions of Maven Site Plugin with Maven 3 won't generate any
reports from reporting plugins,
@@ -97,7 +97,7 @@ Using maven-site-plugin with Maven 3
[]
Notice that Maven 3.0.x reports a misleading warning in case of empty report
plugin version: see
- {{{http://jira.codehaus.org/browse/MNG-5477}MNG-5477}}, fixed in Maven 3.1.0.
+ {{{https://issues.apache.org/jira/browse/MNG-5477}MNG-5477}}, fixed in Maven
3.1.0.
* Site descriptor attachment
@@ -287,7 +287,7 @@ Using maven-site-plugin with Maven 3
public only to help people who used it in previous versions understand why
they need to migrate back to classic configuration.
<Explanation:> The (former) new format did not support report plugins
configuration inheritance, which is crucial for
- usability: see {{{http://jira.codehaus.org/browse/MSITE-484}MSITE-484}}.
This field is technically necessary to remove
+ usability: see
{{{https://issues.apache.org/jira/browse/MSITE-484}MSITE-484}}. This field is
technically necessary to remove
most reporting logic from Maven 3, but a new inheritance mechanism still
needs to be added to make it as flexible as the old format:
we made the field public before finding this crucial limitation and required
to explain later why end-users must not use it, then
cannot use it since <<<maven-site-plugin>>> 3.3.
@@ -348,4 +348,4 @@ Using maven-site-plugin with Maven 3
[]
- For more info see {{{http://jira.codehaus.org/browse/MSITE-596}MSITE-596}}.
+ For more info see
{{{https://issues.apache.org/jira/browse/MSITE-596}MSITE-596}}.
Modified: maven/plugins/trunk/maven-site-plugin/src/site/fml/faq.fml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/fml/faq.fml?rev=1743942&r1=1743941&r2=1743942&view=diff
==============================================================================
--- maven/plugins/trunk/maven-site-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-site-plugin/src/site/fml/faq.fml Sun May 15
18:13:32 2016
@@ -159,7 +159,7 @@ under the License.
</p>
<p>
There is an
- <a href="http://jira.codehaus.org/browse/MSITE-159";>issue for this
in JIRA</a>,
+ <a href="https://issues.apache.org/jira/browse/MSITE-159";>issue for
this in JIRA</a>,
where you can read more about this.
</p>
</answer>
@@ -195,7 +195,7 @@ under the License.
<a href="#Can_I_validate_xml">validation</a> run.
Therefore, if you want to use entities, you <strong>have</strong> to
switch on
validation for your xml source files.
- See <a
href="http://jira.codehaus.org/browse/MSITE-483";>MSITE-483</a>.
+ See <a
href="https://issues.apache.org/jira/browse/MSITE-483";>MSITE-483</a>.
</p>
</answer>
</faq>
