Author: hboutemy
Date: Sat Apr 9 06:05:24 2016
New Revision: 1738325
URL: http://svn.apache.org/viewvc?rev=1738325&view=rev
Log:
changed links to Maven site content to relative
Modified:
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/adding-deploy-protocol.apt.vm
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/configuring-reports.apt
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
maven/plugins/trunk/maven-site-plugin/src/site/apt/index.apt.vm
maven/plugins/trunk/maven-site-plugin/src/site/apt/usage.apt
maven/plugins/trunk/maven-site-plugin/src/site/fml/faq.fml
maven/plugins/trunk/maven-site-plugin/src/site/xdoc/i18n.xml
Modified:
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/adding-deploy-protocol.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/adding-deploy-protocol.apt.vm?rev=1738325&r1=1738324&r2=1738325&view=diff
==============================================================================
---
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/adding-deploy-protocol.apt.vm
(original)
+++
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/adding-deploy-protocol.apt.vm
Sat Apr 9 06:05:24 2016
@@ -43,9 +43,9 @@ Currently supported protocols are: ...
+-----+
As explained in the error message, to deploy a site with a non-built-in
protocol, you need to add the corresponding
- {{{http://maven.apache.org/wagon/}wagon provider}}.
+ {{{/wagon/}wagon provider}}.
- You can add it either as a
{{{http://maven.apache.org/guides/mini/guide-using-extensions.html}global
extension}},
+ You can add it either as a
{{{/guides/mini/guide-using-extensions.html}global extension}},
or declare it at as a dependency of the site plugin:
+-----+
Modified:
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/configuring-reports.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/configuring-reports.apt?rev=1738325&r1=1738324&r2=1738325&view=diff
==============================================================================
---
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/configuring-reports.apt
(original)
+++
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/configuring-reports.apt
Sat Apr 9 06:05:24 2016
@@ -34,7 +34,7 @@ Configuring Reports
current state of the project. These reports take the form of plugin goals,
just
like those used to build the project.
- {{{http://maven.apache.org/plugins/maven-project-info-reports-plugin/}Maven
Project Info Reports Plugin}}
+ {{{/plugins/maven-project-info-reports-plugin/}Maven Project Info Reports
Plugin}}
provides many standard reports by extracting information from the POM, for
example:
* Continous Integration
@@ -54,7 +54,7 @@ Configuring Reports
[]
To find out more please see to the
-
{{{http://maven.apache.org/plugins/maven-project-info-reports-plugin/}Project
Info Reports Plugin}}.
+ {{{/plugins/maven-project-info-reports-plugin/}Project Info Reports Plugin}}.
To add these reports to your site, you must add the plugin to the
<<<\<reporting\>>>> element in the POM. The following example shows how to
@@ -89,7 +89,7 @@ Configuring Reports
the effective output directory to ensure that all reports end up in a common
location.
- Check out reporting plugins ("R" value in the "Type" column) in the
{{{http://maven.apache.org/plugins/}plugins page}},
+ Check out reporting plugins ("R" value in the "Type" column) in the
{{{/plugins/}plugins page}},
for a list of available reporting plugins from Apache Maven Team.
Selecting Reports from a Plugin: Configuring Report Sets
Modified:
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm?rev=1738325&r1=1738324&r2=1738325&view=diff
==============================================================================
---
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
(original)
+++
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
Sat Apr 9 06:05:24 2016
@@ -69,20 +69,20 @@ Creating Content
The APT format ("Almost Plain Text") is a wiki-like format that allows you to
write simple, structured documents (like this one) very quickly. A full
reference of the
- {{{http://maven.apache.org/doxia/references/apt-format.html} APT Format}} is
+ {{{/doxia/references/apt-format.html} APT Format}} is
available.
* FML:
The FML format is the FAQ format. This is the same that were used in Maven
1.x.
For more info about the
- {{{http://maven.apache.org/doxia/references/fml-format.html}FML Format}}
- check the {{{http://maven.apache.org/doxia/}Doxia}} site.
+ {{{/doxia/references/fml-format.html}FML Format}}
+ check the {{{/doxia/}Doxia}} site.
* XDoc:
The XDoc format is the same as
- {{{http://maven.apache.org/maven-1.x/using/site.html} used in Maven 1.x}}.
+ {{{/maven-1.x/using/site.html} used in Maven 1.x}}.
A reference for the
- {{{http://maven.apache.org/doxia/references/xdoc-format.html} XDoc Format}}
+ {{{/doxia/references/xdoc-format.html} XDoc Format}}
is available.
* Markdown (since maven-site-plugin 3.3):
@@ -92,7 +92,7 @@ Creating Content
Other formats are available, but the above four are recognized by default by
the site plugin.
Any other document format for which a Doxia parser exists can be used as
well (see the list of
- {{{http://maven.apache.org/doxia/references/index.html}Doxia Markup
Languages}}),
+ {{{/doxia/references/index.html}Doxia Markup Languages}}),
but in this case you need to add the corresponding Doxia dependency to your
site plugin configuration, as
explained in the last paragraph.
Note that Doxia also supports several output formats, the site plugin only
creates XHTML.
Modified: maven/plugins/trunk/maven-site-plugin/src/site/apt/index.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/index.apt.vm?rev=1738325&r1=1738324&r2=1738325&view=diff
==============================================================================
--- maven/plugins/trunk/maven-site-plugin/src/site/apt/index.apt.vm (original)
+++ maven/plugins/trunk/maven-site-plugin/src/site/apt/index.apt.vm Sat Apr 9
06:05:24 2016
@@ -85,7 +85,7 @@ ${project.name}
entire debug logs, POMs or most preferably little demo projects attached to
the issue are very much appreciated.
Of course, patches are welcome, too. Contributors can check out the project
from our
{{{./source-repository.html}source repository}} and will find supplementary
information in the
- {{{http://maven.apache.org/guides/development/guide-helping.html}guide to
helping with Maven}}.
+ {{{/guides/development/guide-helping.html}guide to helping with Maven}}.
* Examples
Modified: maven/plugins/trunk/maven-site-plugin/src/site/apt/usage.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/usage.apt?rev=1738325&r1=1738324&r2=1738325&view=diff
==============================================================================
--- maven/plugins/trunk/maven-site-plugin/src/site/apt/usage.apt (original)
+++ maven/plugins/trunk/maven-site-plugin/src/site/apt/usage.apt Sat Apr 9
06:05:24 2016
@@ -86,7 +86,7 @@ mvn site
The <<<\<id\>>>> element identifies the repository, so that you can attach
credentials to it in your <<<settings.xml>>> file using the
- {{{http://maven.apache.org/settings.html#Servers}<<<\<servers\>>>> element}}
+ {{{/ref/current/maven-settings/settings.html#Servers}<<<\<servers\>>>>
element}}
as you would for any other repository.
The <<<\<url\>>>> gives the location to deploy to. In the example above we
@@ -148,7 +148,7 @@ mvn site:stage -DstagingDirectory=C:\ful
So if you need to add your username or password separately for stage-deploy
in <<<settings.xml>>>,
you should use <<<\<id\>stagingSite\</id\>>>> for that <<<\<server\>>>>
section.
See the
-
{{{http://maven.apache.org/guides/mini/guide-deployment-security-settings.html}Guide
to Deployment and Security Settings}}
+ {{{/guides/mini/guide-deployment-security-settings.html}Guide to Deployment
and Security Settings}}
for more information on this.
By default, the site will be stage-deployed to
<<<${distributionManagement.site.url}/staging/>>>.
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=1738325&r1=1738324&r2=1738325&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 Sat Apr 9
06:05:24 2016
@@ -29,7 +29,7 @@ under the License.
<dt>mvn site</dt>
<dd>
Calls the <i>site</i> phase of the site lifecycle, which consists
in the following life cycle phases: <code>pre-site</code>, <code>site</code>,
<code>post-site</code> and <code>site-deploy</code>.
- See <a
href="http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference";>Lifecycle
Reference</a>.</dd>
+ See <a
href="/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference">Lifecycle
Reference</a>.</dd>
<dt>mvn site:site</dt>
<dd>Calls the <i>site</i> goal of the site plugin.
See <a href="site-mojo.html">site:site</a>.</dd>
@@ -58,7 +58,7 @@ under the License.
If you want to use a custom format like Twiki, Simple DocBook, or
XHTML
(or any other document format
for which a doxia parser exists, see the list of
- <a href="http://maven.apache.org/doxia/references/index.html";>Doxia
Markup Languages</a>),
+ <a href="/doxia/references/index.html">Doxia Markup Languages</a>),
you need to specify the corresponding Doxia module dependency, e.g.
for Twiki:
</p>
<source>
@@ -104,11 +104,11 @@ under the License.
If validation is switched on, <strong>all</strong> xml source
files need a correct schema and/or DTD definition.
See the Doxia documentation on
- <a
href="http://maven.apache.org/doxia/references/xdoc-format.html#Validation";>validating
xdocs</a>,
+ <a href="/doxia/references/xdoc-format.html#Validation">validating
xdocs</a>,
and the schema definitions for
- <a
href="http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/using-xdoc-xsd.html";>xdoc</a>
+ <a
href="/doxia/doxia/doxia-modules/doxia-module-xdoc/using-xdoc-xsd.html">xdoc</a>
and
- <a
href="http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fml/using-fml-xsd.html";>fml</a>.
+ <a
href="/doxia/doxia/doxia-modules/doxia-module-fml/using-fml-xsd.html">fml</a>.
</p>
</answer>
</faq>
Modified: maven/plugins/trunk/maven-site-plugin/src/site/xdoc/i18n.xml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/xdoc/i18n.xml?rev=1738325&r1=1738324&r2=1738325&view=diff
==============================================================================
--- maven/plugins/trunk/maven-site-plugin/src/site/xdoc/i18n.xml (original)
+++ maven/plugins/trunk/maven-site-plugin/src/site/xdoc/i18n.xml Sat Apr 9
06:05:24 2016
@@ -29,7 +29,7 @@ under the License.
<section name="Internationalization">
<p>
The documentation about internationalization and localization of
plugins has been moved to:
- <a
href="http://maven.apache.org/plugins/localization.html";>http://maven.apache.org/plugins/localization.html</a>
+ <a
href="/plugins/localization.html">http://maven.apache.org/plugins/localization.html</a>
</p>
</section>
</body>
