Author: buildbot
Date: Sun Apr 15 14:23:11 2018
New Revision: 1028458
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html
websites/staging/maven/trunk/content/developers/website/website-overview.html
websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html
websites/staging/maven/trunk/content/docs/2.0.11/release-notes.html
websites/staging/maven/trunk/content/docs/3.0.4/release-notes.html
websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html
websites/staging/maven/trunk/content/guides/development/guide-building-maven.html
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
websites/staging/maven/trunk/content/guides/development/guide-plugin-documentation.html
websites/staging/maven/trunk/content/guides/index.html
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
websites/staging/maven/trunk/content/guides/introduction/introduction-to-repositories.html
websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-local.html
websites/staging/maven/trunk/content/guides/mini/guide-assemblies.html
websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html
websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html
websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html
websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html
websites/staging/maven/trunk/content/guides/mini/guide-relocation.html
websites/staging/maven/trunk/content/guides/mini/guide-site.html
websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
websites/staging/maven/trunk/content/plugin-developers/common-bugs.html
websites/staging/maven/trunk/content/pom.html
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Apr 15 14:23:11 2018
@@ -1 +1 @@
-1829207
+1829209
Modified:
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
==============================================================================
---
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
(original)
+++
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
Sun Apr 15 14:23:11 2018
@@ -135,7 +135,7 @@ Hervé Boutemy" />
<div id="bodyColumn" class="span10" >
<div class="section">
<h2><a name="Introduction"></a>Introduction</h2>
-<p>This document gives step-by-step instructions for deploying Maven
components reference documentation inside the Maven <a class="externalLink"
href="http://maven.apache.org/";>http://maven.apache.org/</a> website.</p>
+<p>This document gives step-by-step instructions for deploying Maven
components reference documentation inside the Maven <a
href="/">http:s//maven.apache.org/</a> website.</p>
<p>See <a href="./index.html">Maven website introduction</a> for instructions
on the whole website publication (main site content + components).</p></div>
<div class="section">
<h2><a name="Overview"></a>Overview</h2>
Modified:
websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html
==============================================================================
---
websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html
(original)
+++
websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html
Sun Apr 15 14:23:11 2018
@@ -123,14 +123,14 @@ Hervé Boutemy" />
<div id="bodyColumn" class="span10" >
<div class="section">
<h2><a name="Introduction"></a>Introduction</h2>
-<p>This document gives step-by-step instructions for deploying the main Maven
<a class="externalLink"
href="http://maven.apache.org";>http://maven.apache.org</a> website.</p>
+<p>This document gives step-by-step instructions for deploying the main Maven
<a href="/">https://maven.apache.org</a> website.</p>
<p>See <a href="./index.html">Maven website introduction</a> for instructions
on the whole website publication.</p></div>
<div class="section">
<h2><a name="Overview"></a>Overview</h2>
<p>Since December 2012, the overall website uses svnpubsub mechanism and the
main website uses Apache CMS:</p><img src="main-website.png" alt="Main website
mechanisms overview" /></div>
<div class="section">
<h2><a name="How_main_website_publication_works"></a>How main website
publication works</h2>
-<p>Maven main website (<a class="externalLink"
href="http://maven.apache.org";>http://maven.apache.org</a>) is generated with
<a href="/plugins/maven-site-plugin">maven-site-plugin</a> from a source tree
stored in svn: <a class="externalLink"
href="https://svn.apache.org/repos/asf/maven/site/trunk";>https://svn.apache.org/repos/asf/maven/site/trunk</a>.</p>
+<p>Maven main website (<a class="externalLink"
href="https://maven.apache.org";>https://maven.apache.org</a>) is generated with
<a href="/plugins/maven-site-plugin">maven-site-plugin</a> from a source tree
stored in svn: <a class="externalLink"
href="https://svn.apache.org/repos/asf/maven/site/trunk";>https://svn.apache.org/repos/asf/maven/site/trunk</a>.</p>
<div class="section">
<h3><a name="Edit_source_content"></a>Edit source content</h3>
<p>You can edit source content in 2 ways:</p>
@@ -163,7 +163,7 @@ Hervé Boutemy" />
<li>svnpubsub published to <a class="externalLink"
href="http://maven-doxia.staging.apache.org";>live staging site</a>,</li>
<li>if everything is good, <b>publish modifications</b> using <a
class="externalLink" href="https://cms.apache.org/maven-doxia/publish";>CMS
publish</a> action,</li>
<li>CMS copies CMS staging svn area content to <a class="externalLink"
href="https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/";>website
production svn area</a>,</li>
-<li>svnpubsub mecanism transfers svn production content to live production
site: <a class="externalLink"
href="http://maven.apache.org/doxia";>http://maven.apache.org/doxia</a>, with
its <a class="externalLink"
href="http://maven.apache.org/doxia/extpaths.txt";><tt>extpaths.txt</tt></a></li></ul></div>
+<li>svnpubsub mecanism transfers svn production content to live production
site: <a class="externalLink"
href="http://maven.apache.org/doxia";>http://maven.apache.org/doxia</a>, with
its <a href="/doxia/extpaths.txt"><tt>extpaths.txt</tt></a></li></ul></div>
</div>
</div>
</div>
Modified:
websites/staging/maven/trunk/content/developers/website/website-overview.html
==============================================================================
---
websites/staging/maven/trunk/content/developers/website/website-overview.html
(original)
+++
websites/staging/maven/trunk/content/developers/website/website-overview.html
Sun Apr 15 14:23:11 2018
@@ -123,7 +123,7 @@ Hervé Boutemy" />
<div id="bodyColumn" class="span10" >
<div class="section">
<h2><a name="Introduction"></a>Introduction</h2>
-<p>The Maven <a class="externalLink"
href="http://maven.apache.org";>http://maven.apache.org</a> website is composed
from:</p>
+<p>The Maven <a href="/">https://maven.apache.org</a> website is composed
from:</p>
<ul>
<li>a main content</li>
<li>multiple components reference documentation</li></ul><img
src="website-overview.png" alt="Website mechanisms overview" />
Modified:
websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html
==============================================================================
---
websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html
(original)
+++
websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html
Sun Apr 15 14:23:11 2018
@@ -132,7 +132,7 @@
<li><a class="externalLink"
href="http://www.apache.org/foundation/voting.html";>How voting works</a>
</li></ul>
<p>Here are the documents that pertain to Maven specifically:</p>
<ul>
-<li><a class="externalLink"
href="http://maven.apache.org/guides/development/guide-maven-development.html";>Guide
to Maven development</a></li></ul>
+<li><a href="/guides/development/guide-maven-development.html">Guide to Maven
development</a></li></ul>
<p>And here are the specifics on setting up your SVN access:</p>
<ul>
<li><a class="externalLink"
href="http://www.apache.org/dev/version-control.html";>Apache's Source Code
Repository</a></li></ul>
Modified: websites/staging/maven/trunk/content/docs/2.0.11/release-notes.html
==============================================================================
--- websites/staging/maven/trunk/content/docs/2.0.11/release-notes.html
(original)
+++ websites/staging/maven/trunk/content/docs/2.0.11/release-notes.html Sun Apr
15 14:23:11 2018
@@ -123,13 +123,13 @@
<div class="section">
<h2><a name="Maven_2.0.11"></a>Maven 2.0.11</h2>
<p>The Apache Maven team would like to announce the release of Maven
2.0.11.</p>
-<p>Maven 2.0.11 is <a class="externalLink"
href="http://maven.apache.org/download.html";> available for download</a>.</p>
+<p>Maven 2.0.11 is <a href="/download.html"> available for download</a>.</p>
<p>Maven is a software project management and comprehension tool. Based on the
concept of a project object model (POM), Maven can manage a project's build,
reporting and documentation from a central place.</p>
-<p>The core release is independent of the plugins available. Further releases
of plugins will be made separately. See the <a class="externalLink"
href="http://maven.apache.org/plugins/index.html";> Plugin List</a> for more
information.</p>
+<p>The core release is independent of the plugins available. Further releases
of plugins will be made separately. See the <a href="/plugins/index.html">
Plugin List</a> for more information.</p>
<p>We hope you enjoy using Maven! If you have any questions, please
consult:</p>
<ul>
-<li>the web site: <a class="externalLink"
href="http://maven.apache.org/";>http://maven.apache.org/</a></li>
-<li>the maven-user mailing list: <a class="externalLink"
href="http://maven.apache.org/mail-lists.html";>http://maven.apache.org/mail-lists.html</a></li></ul>
+<li>the web site: <a class="externalLink"
href="https://maven.apache.org/";>https://maven.apache.org/</a></li>
+<li>the maven-user mailing list: <a class="externalLink"
href="https://maven.apache.org/mail-lists.html";>https://maven.apache.org/mail-lists.html</a></li></ul>
<p>For news and information, see:</p>
<ul>
<li>Maven Dashboard: <a class="externalLink"
href="http://docs.codehaus.org/display/MAVEN/Home";>http://docs.codehaus.org/display/MAVEN/Home</a></li></ul>
Modified: websites/staging/maven/trunk/content/docs/3.0.4/release-notes.html
==============================================================================
--- websites/staging/maven/trunk/content/docs/3.0.4/release-notes.html
(original)
+++ websites/staging/maven/trunk/content/docs/3.0.4/release-notes.html Sun Apr
15 14:23:11 2018
@@ -126,7 +126,7 @@
<p>Maven 3.0.4 is <a href="../../download.html"> available for
download</a>.</p>
<p>Maven is a software project management and comprehension tool. Based on the
concept of a project object model (POM), Maven can manage a project's build,
reporting and documentation from a central place.</p>
<p>Maven 3 aims to ensure backward compatibility with Maven 2, improve
usability, increase performance, allow safe embedding, and pave the way to
implement many highly demanded features.</p>
-<p><b>NOTE:</b> Maven 3.0.4 has a new default Http Wagon based on Apache
HttpClient 4.1.2. You must read various available settings documented <a
class="externalLink"
href="http://maven.apache.org/guides/mini/guide-http-settings.html";>here</a>.</p>
+<p><b>NOTE:</b> Maven 3.0.4 has a new default Http Wagon based on Apache
HttpClient 4.1.2. You must read various available settings documented <a
href="/guides/mini/guide-http-settings.html">here</a>.</p>
<p>Some enhancements are now included by default:</p>
<ul>
<li>http(s) connection pool.</li>
Modified:
websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html
==============================================================================
---
websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html
(original)
+++
websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html
Sun Apr 15 14:23:11 2018
@@ -124,7 +124,7 @@
<h2><a name="Example:_Using_Maven_3_lifecycle_extension"></a>Example: Using
Maven 3 lifecycle extension</h2>
<div class="section">
<h3><a name="Lifecyle_Participation"></a>Lifecyle Participation</h3>
-<p>You can extends the class
<tt>org.apache.maven.AbstractMavenLifecycleParticipant</tt> see <a
class="externalLink"
href="http://maven.apache.org/ref/current/apidocs/org/apache/maven/AbstractMavenLifecycleParticipant.html";>javadoc</a>.</p></div>
+<p>You can extends the class
<tt>org.apache.maven.AbstractMavenLifecycleParticipant</tt> see <a
href="/ref/current/apidocs/org/apache/maven/AbstractMavenLifecycleParticipant.html">javadoc</a>.</p></div>
<div class="section">
<h3><a name="Build_your_extension"></a>Build your extension</h3>
<p>Create a Maven project with a dependency on
org.apache.maven:maven-core:3.5.3 and other dependencies :</p>
Modified:
websites/staging/maven/trunk/content/guides/development/guide-building-maven.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/development/guide-building-maven.html
(original)
+++
websites/staging/maven/trunk/content/guides/development/guide-building-maven.html
Sun Apr 15 14:23:11 2018
@@ -143,7 +143,7 @@ Jason van Zyl" />
<p>Note, that you don't need to bootstrap Maven for day to day use, or to
develop plugins. While we encourage getting involved and fixing bugs that you
find, for day to day use we recommend using the latest release.</p></div>
<div class="section">
<h3><a name="Checking_out_the_sources"></a>Checking out the sources</h3>
-<p>All of the source code for Maven and its related libraries is in managed in
the ASF source code repositories. Current development of the core of Maven, and
some other components, are in git. Other pieces (and older versions) are in
Subversion. For details, see <a class="externalLink"
href="http://maven.apache.org/source-repository.html";>http://maven.apache.org/source-repository.html</a>.</p></div>
+<p>All of the source code for Maven and its related libraries is in managed in
the ASF source code repositories. Current development of the core of Maven, and
some other components, are in git. Other pieces (and older versions) are in
Subversion. For details, see <a
href="/source-repository.html">https://maven.apache.org/source-repository.html</a>.</p></div>
<div class="section">
<h3><a name="Building_Maven"></a>Building Maven</h3>
<div class="section">
Modified:
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
(original)
+++
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
Sun Apr 15 14:23:11 2018
@@ -206,10 +206,10 @@ Brett Porter" />
<p>You can read more about <a href="/doxia/">Doxia</a> and the currently
supported <a href="/doxia/references/index.html">document formats</a>.</p></li>
<li>Maven SCM
<p>Maven SCM (Source Control Management) is an reusable API which is
independent of Maven itself and it is used by the SCM related Maven Plugins.
The core part of Maven itself doesn't depend on Maven SCM.</p>
-<p>You can <a class="externalLink" href="http://maven.apache.org/scm/";>read
more about Scm</a>.</p></li>
+<p>You can <a href="/scm/">read more about Scm</a>.</p></li>
<li>Maven Wagon
<p>Maven Wagon is also a standalone API that deals with transporting files and
directories. Maven Core uses the Wagon API to download and upload artifacts and
artifact metadata and the site plug-in uses it to publish the site.</p>
-<p>You can <a class="externalLink" href="http://maven.apache.org/wagon/";>read
more about Wagon</a>.</p></li></ul></div>
+<p>You can <a href="/wagon/">read more about Wagon</a>.</p></li></ul></div>
<div class="section">
<h3><a name="Further_Links">Further Links</a></h3>
<ul>
Modified:
websites/staging/maven/trunk/content/guides/development/guide-plugin-documentation.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/development/guide-plugin-documentation.html
(original)
+++
websites/staging/maven/trunk/content/guides/development/guide-plugin-documentation.html
Sun Apr 15 14:23:11 2018
@@ -133,7 +133,7 @@
<p>It is recommended that you let Maven generate the basic information for the
plugin to make sure that that the basic information is always accurate and
synchronized with the plugin implementation. </p>
<p>Documentation is generated by running </p>
<div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
-<p>It will generate a plugin site based on the information in the POM,
<tt>src/site</tt> and other reporting plugins configured in the POM. The most
important reporting plugin is the <a class="externalLink"
href="http://maven.apache.org/plugins/maven-plugin-plugin/";>Maven Plugin
Plugin</a> which will generate the documentation for each plugin goal based on
the mojo annotations. But in order for the generated site to be usable, the
required information should be available to the Maven Site Plugin.</p>
+<p>It will generate a plugin site based on the information in the POM,
<tt>src/site</tt> and other reporting plugins configured in the POM. The most
important reporting plugin is the <a href="/plugins/maven-plugin-plugin/">Maven
Plugin Plugin</a> which will generate the documentation for each plugin goal
based on the mojo annotations. But in order for the generated site to be
usable, the required information should be available to the Maven Site
Plugin.</p>
<div class="section">
<h3><a name="POM_Elements"></a>POM Elements</h3>
<p>Maven extracts the information from the POM to generate the pages under
Project Information. The first step in having a good documentation is to have
an accurate and visible basic project information, Maven can provide this for
the plugin as long as the information in the POM is complete, descriptive and
accurate.</p>
@@ -307,16 +307,16 @@ Plugin 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
To provide you with better understanding of some usages of the Plugin Name,
you can take a look into the following examples:
- * {{{examples/example-one.html}Example Description One}}
+ * {{{./examples/example-one.html}Example Description One}}
- * {{{examples/example-two.html}Example Description Two}}
+ * {{{./examples/example-two.html}Example Description Two}}
</pre></div></li>
<li>Goals
<p><tt>plugin-info.html</tt> is generated by the Maven Plugin Plugin. Until
the Maven Site Plugin is updated it would be better to pull it out to the main
menu for greater visibility. This contains the goals and their descriptions
with a link to the configuration parameters. The information is based on the
comments and annotations of the plugin. </p></li>
@@ -341,8 +341,8 @@ Plugin Name
<p>The advanced configurations and examples not covered in the usage page is
located here. Advanced users who wants to maximize the use of a plugin can
check the items here. Tips on how to use the plugin effectively is also a good
thing to put here.</p>
<p>For examples of items under "Examples" check these plugin
sites:</p>
<ul>
-<li><a class="externalLink"
href="http://maven.apache.org/plugins/maven-javadoc-plugin/";>Maven Javadoc
Plugin Examples</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/plugins/maven-war-plugin/";>Maven War Plugin
Examples</a></li></ul></li></ul></div></div></div>
+<li><a href="/plugins/maven-javadoc-plugin/">Maven Javadoc Plugin
Examples</a></li>
+<li><a href="/plugins/maven-war-plugin/">Maven War Plugin
Examples</a></li></ul></li></ul></div></div></div>
<div class="section">
<h3><a name="Recommended_Configured_Reports"></a>Recommended Configured
Reports</h3>
<p>There are 2 recommended report plugins to enhance the plugin documentation,
Javadoc and JXR.</p>
@@ -370,7 +370,7 @@ Plugin Name
[...]
</reporting>
[...]</pre></div>
-<p>Check the documentation about the plugin's <a class="externalLink"
href="http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html";><tt>javadoc:javadoc</tt></a>
goal for the advanced configurations.</p></li>
+<p>Check the documentation about the plugin's <a
href="/plugins/maven-javadoc-plugin/javadoc-mojo.html"><tt>javadoc:javadoc</tt></a>
goal for the advanced configurations.</p></li>
<li>Maven JXR Plugin
<p>The Maven JXR Plugin generates a cross-reference of the project sources.
The generated cross-references are also linked to the corresponding javadoc if
javadoc is generated. The cross-references is great for those who wants to
better understand the inner workings of the plugin.</p>
<p>To enable source code cross-references add the following to your
<tt>pom.xml</tt></p>
@@ -388,7 +388,7 @@ Plugin Name
</plugins>
</reporting>
[...] </pre></div>
-<p>Check the <a class="externalLink"
href="http://maven.apache.org/plugins/maven-jxr-plugin/jxr-mojo.html";>JXR
configuration page</a> for the possible configuration
parameters.</p></li></ul></div></div>
+<p>Check the <a href="/plugins/maven-jxr-plugin/jxr-mojo.html">JXR
configuration page</a> for the possible configuration
parameters.</p></li></ul></div></div>
</div>
</div>
</div>
Modified: websites/staging/maven/trunk/content/guides/index.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/index.html (original)
+++ websites/staging/maven/trunk/content/guides/index.html Sun Apr 15 14:23:11
2018
@@ -150,7 +150,7 @@ Eric Redmond" />
<h4><a name="Site"></a>Site</h4>
<ul>
<li><a href="./mini/guide-site.html">Creating a Site</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/doxia/references/apt-format.html";>The APT
Format</a></li>
+<li><a href="/doxia/references/apt-format.html">The APT Format</a></li>
<li><a href="./mini/guide-snippet-macro.html">Snippet Macro</a></li></ul></div>
<div class="section">
<h4><a name="Archetypes"></a>Archetypes</h4>
@@ -222,7 +222,7 @@ Eric Redmond" />
<h4><a name="The_Central_Repository"></a>The Central Repository</h4>
<ul>
<li><a href="/repository/">Introduction to the Central Repository</a></li>
-<li><a href="./mini/guide-central-repository-upload.html">Uploading Artifacts
to the Central Repository</a></li>
+<li><a href="/repository/guide-central-repository-upload.html">Uploading
Artifacts to the Central Repository</a></li>
<li><a href="/repository/central-metadata.html">Improving the
Repository</a></li></ul></div></div>
<div class="section">
<h3><a name="References"></a>References</h3>
@@ -237,13 +237,13 @@ Eric Redmond" />
<h3><a name="Javadoc_API"></a>Javadoc API</h3>
<p>Here is some useful Javadoc API links to the current version of Maven:</p>
<ul>
-<li><a class="externalLink"
href="http://maven.apache.org/ref/current/maven-artifact/apidocs/";>Maven
Artifact</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/shared/maven-reporting-api/apidocs/";>Maven
Reporting</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/ref/current/maven-plugin-api/apidocs/";>Maven
Plugin API</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/ref/current/maven-model/apidocs/";>Maven
Model</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/ref/current/maven-core/apidocs/";>Maven
Core</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/ref/current/maven-settings/apidocs/";>Maven
Settings</a></li></ul>
-<p>You could also browse the <a class="externalLink"
href="http://maven.apache.org/ref/current/";>full technical documentation
references</a> of the current version of Maven.</p></div></div>
+<li><a href="/ref/current/maven-artifact/apidocs/">Maven Artifact</a></li>
+<li><a href="/shared/maven-reporting-api/apidocs/">Maven Reporting</a></li>
+<li><a href="/ref/current/maven-plugin-api/apidocs/">Maven Plugin API</a></li>
+<li><a href="/ref/current/maven-model/apidocs/">Maven Model</a></li>
+<li><a href="/ref/current/maven-core/apidocs/">Maven Core</a></li>
+<li><a href="/ref/current/maven-settings/apidocs/">Maven Settings</a></li></ul>
+<p>You could also browse the <a href="/ref/current/">full technical
documentation references</a> of the current version of Maven.</p></div></div>
</div>
</div>
</div>
Modified:
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
(original)
+++
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
Sun Apr 15 14:23:11 2018
@@ -154,11 +154,11 @@
<li>Per Project
<p>- Defined in the POM itself <tt>(pom.xml)</tt>.</p></li>
<li>Per User
-<p>- Defined in the <a class="externalLink"
href="http://maven.apache.org/ref/2.2.1/maven-settings/settings.html";>
Maven-settings</a> <tt>(%USER_HOME%/.m2/settings.xml)</tt>.</p></li>
+<p>- Defined in the <a href="/ref/current/maven-settings/settings.html">
Maven-settings</a> <tt>(%USER_HOME%/.m2/settings.xml)</tt>.</p></li>
<li>Global
-<p>- Defined in the <a class="externalLink"
href="http://maven.apache.org/ref/2.2.1/maven-settings/settings.html";> global
Maven-settings</a> <tt>(${maven.home}/conf/settings.xml)</tt>.</p></li>
+<p>- Defined in the <a href="/ref/current/maven-settings/settings.html">
global Maven-settings</a> <tt>(${maven.home}/conf/settings.xml)</tt>.</p></li>
<li>Profile descriptor
-<p>- a descriptor located in <a class="externalLink"
href="http://maven.apache.org/ref/2.2.1/maven-profile/profiles.html";>project
basedir <tt>(profiles.xml)</tt></a> (unsupported in Maven 3.0: see <a
class="externalLink"
href="https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-profiles.xml";>
Maven 3 compatibility notes</a>)</p></li></ul></div>
+<p>- a descriptor located in <a
href="/ref/2.2.1/maven-profile/profiles.html">project basedir
<tt>(profiles.xml)</tt></a> (unsupported in Maven 3.0: see <a
class="externalLink"
href="https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-profiles.xml";>
Maven 3 compatibility notes</a>)</p></li></ul></div>
<div class="section">
<h3><a
name="How_can_a_profile_be_triggered.3F_How_does_this_vary_according_to_the_type_of_profile_being_used.3F"></a>How
can a profile be triggered? How does this vary according to the type of
profile being used?</h3>
<p>A profile can be triggered/activated in several ways:</p>
@@ -192,7 +192,7 @@
...
</profile>
</profiles></pre></div>
-<p>Ranges can also be used as of Maven 2.1 (refer to the <a
class="externalLink"
href="http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html";>
Enforcer Version Range Syntax</a> for more information). The following honours
versions 1.3, 1.4 and 1.5.</p>
+<p>Ranges can also be used as of Maven 2.1 (refer to the <a
href="/enforcer/enforcer-rules/versionRanges.html"> Enforcer Version Range
Syntax</a> for more information). The following honours versions 1.3, 1.4 and
1.5.</p>
<div class="source"><pre class="prettyprint linenums"><profiles>
<profile>
<activation>
@@ -202,7 +202,7 @@
</profile>
</profiles></pre></div>
<p><i>Note:</i> an upper bound such as <tt>,1.5]</tt> is likely not to include
most releases of 1.5, since they will have an additional "patch"
release such as <tt>_05</tt> that is not taken into consideration in the above
range.</p>
-<p>This next one will activate based on OS settings. See the <a
class="externalLink"
href="http://maven.apache.org/enforcer/enforcer-rules/requireOS.html";>Maven
Enforcer Plugin</a> for more details about OS values.</p>
+<p>This next one will activate based on OS settings. See the <a
href="/enforcer/enforcer-rules/requireOS.html">Maven Enforcer Plugin</a> for
more details about OS values.</p>
<div class="source"><pre class="prettyprint linenums"><profiles>
<profile>
<activation>
@@ -436,7 +436,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<p>As a quick aside, it's possible for user-specific profiles to act in a
similar way. This means that profiles for handling different environments which
are keyed to the user can act up when the team adds a new developer. While I
suppose this <i>could</i> act as useful training for the newbie, it just
wouldn't be nice to throw them to the wolves in this way. Again, be sure to
think of the <i>whole</i> set of profiles.</p></div></div>
<div class="section">
<h3><a
name="How_can_I_tell_which_profiles_are_in_effect_during_a_build.3F"></a>How
can I tell which profiles are in effect during a build?</h3>
-<p>Determining active profiles will help the user to know what particular
profiles has been executed during a build. We can use the <a
class="externalLink"
href="http://maven.apache.org/plugins/maven-help-plugin/";>Maven Help Plugin</a>
to tell what profiles are in effect during a build.</p>
+<p>Determining active profiles will help the user to know what particular
profiles has been executed during a build. We can use the <a
href="/plugins/maven-help-plugin/">Maven Help Plugin</a> to tell what profiles
are in effect during a build.</p>
<div class="source"><pre class="prettyprint linenums"> mvn
help:active-profiles</pre></div>
<p>Let us have some small samples that will help us to understand more on the
<i>active-profiles</i> goal of that plugin.</p>
<p>From the last example of profiles in the <tt>pom.xml</tt>, you'll notice
that there are two profiles named <tt>appserverConfig-dev</tt> and
<tt>appserverConfig-dev-2</tt> which has been given different values for
properties. If we go ahead and execute:</p>
Modified:
websites/staging/maven/trunk/content/guides/introduction/introduction-to-repositories.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/introduction/introduction-to-repositories.html
(original)
+++
websites/staging/maven/trunk/content/guides/introduction/introduction-to-repositories.html
Sun Apr 15 14:23:11 2018
@@ -214,7 +214,7 @@ Brian Fox" />
<div class="section">
<h3><a name="Deploying_to_the_Internal_Repository"></a>Deploying to the
Internal Repository</h3>
<p>One of the most important reasons to have one or more internal repositories
is to be able to publish your own private releases to share.</p>
-<p>To publish to the repository, you will need to have access via one of SCP,
SFTP, FTP, WebDAV, or the filesystem. Connectivity is accomplished with the
various <a class="externalLink"
href="http://maven.apache.org/wagon/wagon-providers/index.html";>wagons</a>.
Some wagons may need to be added as <a class="externalLink"
href="http://maven.apache.org/ref/current/maven-model/maven.html#class_extension";>extension</a>
to your build.</p></div></div>
+<p>To publish to the repository, you will need to have access via one of SCP,
SFTP, FTP, WebDAV, or the filesystem. Connectivity is accomplished with the
various <a href="/wagon/wagon-providers/index.html">wagons</a>. Some wagons may
need to be added as <a
href="/ref/current/maven-model/maven.html#class_extension">extension</a> to
your build.</p></div></div>
</div>
</div>
</div>
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-local.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-local.html
(original)
+++
websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-local.html
Sun Apr 15 14:23:11 2018
@@ -146,7 +146,7 @@ Robert Scholte" />
<div id="bodyColumn" class="span10" >
<div class="section">
<h2><a name="Guide_to_installing_3rd_party_JARs"></a>Guide to installing 3rd
party JARs</h2>
-<p>Although rarely, but sometimes you will have 3rd party JARs that you need
to put in your local repository for use in your builds, since they don't exist
in any public repository like <a class="externalLink"
href="http://search.maven.org";>Maven Central</a>. The JARs must be placed in
the local repository in the correct place in order for it to be correctly
picked up by Apache Maven. To make this easier, and less error prone, we have
provide a goal in the <a class="externalLink"
href="http://maven.apache.org/plugins/maven-install-plugin/";>maven-install-plugin</a>
which should make this relatively painless. To install a JAR in the local
repository use the following command:</p>
+<p>Although rarely, but sometimes you will have 3rd party JARs that you need
to put in your local repository for use in your builds, since they don't exist
in any public repository like <a class="externalLink"
href="http://search.maven.org";>Maven Central</a>. The JARs must be placed in
the local repository in the correct place in order for it to be correctly
picked up by Apache Maven. To make this easier, and less error prone, we have
provide a goal in the <a
href="/plugins/maven-install-plugin/">maven-install-plugin</a> which should
make this relatively painless. To install a JAR in the local repository use the
following command:</p>
<div class="source"><pre class="prettyprint linenums">
mvn install:install-file -Dfile=<path-to-file>
-DgroupId=<group-id> \
-DartifactId=<artifact-id> -Dversion=<version>
-Dpackaging=<packaging>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-assemblies.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-assemblies.html
(original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-assemblies.html Sun
Apr 15 14:23:11 2018
@@ -232,8 +232,8 @@
</fileSet>
</fileSets>
</assembly></pre></div>
-<p>You can use a manually defined assembly descriptor as mentioned before but
it is simpler to use the <a class="externalLink"
href="http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#bin";>pre-defined
assembly descriptor bin</a> in such cases.</p>
-<p>How to use such pre-defined assembly descriptors is described in the <a
class="externalLink"
href="http://maven.apache.org/plugins/maven-assembly-plugin/usage.html#Configuration";>documentation
of maven-assembly-plugin</a>.</p>
+<p>You can use a manually defined assembly descriptor as mentioned before but
it is simpler to use the <a
href="/plugins/maven-assembly-plugin/descriptor-refs.html#bin">pre-defined
assembly descriptor bin</a> in such cases.</p>
+<p>How to use such pre-defined assembly descriptors is described in the <a
href="/plugins/maven-assembly-plugin/usage.html#Configuration">documentation of
maven-assembly-plugin</a>.</p>
<div class="source"><pre class="prettyprint linenums"><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -270,7 +270,7 @@
</dependencySets>
</assembly>
</pre></div>
-<p>If you like to create a source distribution package the best solution is to
use the <a class="externalLink"
href="http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#src";>pre-defined
assembly descriptor src</a> for such purposes.</p>
+<p>If you like to create a source distribution package the best solution is to
use the <a
href="/plugins/maven-assembly-plugin/descriptor-refs.html#src">pre-defined
assembly descriptor src</a> for such purposes.</p>
<div class="source"><pre class="prettyprint linenums"><assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd">
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html
(original)
+++
websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html
Sun Apr 15 14:23:11 2018
@@ -171,7 +171,7 @@ Vincent Siveton" />
<ul>
<li><b>Build plugins</b> will be executed during the build and then, they
should be configured in the <tt><build/></tt> element.</li>
<li><b>Reporting plugins</b> will be executed during the site generation and
they should be configured in the <tt><reporting/></tt> element.</li></ul>
-<p>All plugins should have minimal required <a class="externalLink"
href="http://maven.apache.org/ref/current/maven-model/maven.html#class_plugin";>informations</a>:
<tt>groupId</tt>, <tt>artifactId</tt> and <tt>version</tt>.</p>
+<p>All plugins should have minimal required <a
href="/ref/current/maven-model/maven.html#class_plugin">informations</a>:
<tt>groupId</tt>, <tt>artifactId</tt> and <tt>version</tt>.</p>
<p><b>Important Note</b>: It is recommended to always defined each version of
the plugins used by the build to guarantee the build reproducibility. A good
practice is to specify them in the
<tt><build><pluginManagement/></build></tt> elements for
<b>each</b> build plugins (generally, you will define a
<pluginManagement/> element in a parent POM). For reporting plugins, you
should specify each version in the
<tt><reporting><plugins/></reporting></tt> elements (and
surely in the <tt><build><pluginManagement/></build></tt>
elements too).</p></div>
<div class="section">
<h3><a name="Generic_Configuration">Generic Configuration</a></h3>
@@ -233,7 +233,7 @@ public class MyQueryMojo
<h4><a name="Help_Goal">Help Goal</a></h4>
<p>Recent Maven plugins have generally an <tt>help</tt> goal to have in the
command line the description of the plugin, with their parameters and types.
For instance, to understand the javadoc goal, you need to call:</p>
<div class="source"><pre class="prettyprint linenums">mvn javadoc:help
-Ddetail -Dgoal=javadoc</pre></div>
-<p>And you will see all parameters for the javadoc:javadoc goal, similar to
this <a class="externalLink"
href="http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html";>page</a>.</p></div>
+<p>And you will see all parameters for the javadoc:javadoc goal, similar to
this <a
href="/plugins/maven-javadoc-plugin/javadoc-mojo.html">page</a>.</p></div>
<div class="section">
<h4><a name="Configuring_Parameters">Configuring Parameters</a></h4>
<div class="section">
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html
(original)
+++
websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html
Sun Apr 15 14:23:11 2018
@@ -166,7 +166,7 @@
<p>All you need to specify is a <tt>groupId</tt>, <tt>artifactId</tt> and
<tt>version</tt>. These three parameters will be needed later for invoking the
archetype via <tt>archetype:generate</tt> from the commandline.</p></div>
<div class="section">
<h3><a name="a2._Create_the_archetype_descriptor"></a>2. Create the archetype
descriptor</h3>
-<p>The <a class="externalLink"
href="http://maven.apache.org/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html";>archetype
descriptor</a> is a file called <tt>archetype.xml</tt> which must be located
in the <tt>src/main/resources/META-INF/maven/</tt> directory. An example of an
archetype descriptor can be found in the quickstart archetype:</p>
+<p>The <a
href="/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html">archetype
descriptor</a> is a file called <tt>archetype.xml</tt> which must be located
in the <tt>src/main/resources/META-INF/maven/</tt> directory. An example of an
archetype descriptor can be found in the quickstart archetype:</p>
<div class="source"><pre class="prettyprint linenums">
<archetype
xmlns="http://maven.apache.org/plugins/maven-archetype-plugin/archetype/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-archetype-plugin/archetype/1.0.0
http://maven.apache.org/xsd/archetype-1.0.0.xsd">
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html
(original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html
Sun Apr 15 14:23:11 2018
@@ -462,7 +462,7 @@ problems with HTTP servers and proxies t
<li><a class="externalLink"
href="http://hc.apache.org/httpclient-3.x/";>HttpClient website</a></li>
<li><a class="externalLink"
href="http://hc.apache.org/httpclient-3.x/preference-api.html";>HttpClient
preference architecture and configuration guide</a></li>
<li><a href="./guide-wagon-providers.html">Guide to Wagon Providers</a></li>
-<li><a class="externalLink"
href="http://maven.apache.org/wagon/wagon-providers/wagon-http/";>Wagon
Http</a></li></ol></div></div>
+<li><a href="/wagon/wagon-providers/wagon-http/">Wagon
Http</a></li></ol></div></div>
</div>
</div>
</div>
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html
(original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html
Sun Apr 15 14:23:11 2018
@@ -164,7 +164,7 @@ Robert Scholte" />
<div id="bodyColumn" class="span10" >
<div class="section">
<h2><a name="Using_Mirrors_for_Repositories"></a>Using Mirrors for
Repositories</h2>
-<p>With <a class="externalLink"
href="http://maven.apache.org/guides/introduction/introduction-to-repositories.html";>Repositories</a>
you specify from which locations you want to <i>download</i> certain
artifacts, such as dependencies and maven-plugins. Repositories can be declared
inside a project, which means that if you have your own custom repositories,
those sharing your project easily get the right settings out of the box.
However, you may want to use an alternative mirror for a particular repository
without changing the project files.</p>
+<p>With <a
href="/guides/introduction/introduction-to-repositories.html">Repositories</a>
you specify from which locations you want to <i>download</i> certain artifacts,
such as dependencies and maven-plugins. Repositories can be declared inside a
project, which means that if you have your own custom repositories, those
sharing your project easily get the right settings out of the box. However, you
may want to use an alternative mirror for a particular repository without
changing the project files.</p>
<p>Some reasons to use a mirror are:</p>
<ul>
<li>There is a synchronized mirror on the internet that is geographically
closer and faster</li>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-relocation.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-relocation.html
(original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-relocation.html Sun
Apr 15 14:23:11 2018
@@ -184,7 +184,7 @@
</relocation>
</distributionManagement>
</project></pre></div>
-<p>In this case we are relocating because the groupId has changed. We only
need to add the element that has changed to the <tt>relocation</tt> element.
For information on which elements are allowed in the <tt>relocation</tt>
element, see <a class="externalLink"
href="http://maven.apache.org/ref/current/maven-model/maven.html#class_relocation";>the
pom reference</a>.</p></li>
+<p>In this case we are relocating because the groupId has changed. We only
need to add the element that has changed to the <tt>relocation</tt> element.
For information on which elements are allowed in the <tt>relocation</tt>
element, see <a href="/ref/current/maven-model/maven.html#class_relocation">the
pom reference</a>.</p></li>
<li>If your project uses MD5 or SHA1 checksums you must now create new
checksums for the pom files in <tt>/bar/foo/</tt> in your Maven 2 repository.
If the pom file needs to be signed, do that as well.</li>
<li>If your project syncs with ibiblio, you should now initiate that sync.
This might happen automatically depending on your projects sync
policy.</li></ol>
<p>Your <tt>foo</tt>-artifacts are now available to Maven 2 users with both
the old and the new groupId. Projects using the old groupId will automatically
be redirected to the new groupId and a warning telling the user to update their
dependencies will be issued.</p>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-site.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-site.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-site.html Sun Apr 15
14:23:11 2018
@@ -164,13 +164,13 @@ Jason van Zyl" />
|
+- site.xml</pre></div>
<p>You will notice there is now a <tt>${basedir}/src/site</tt> directory
within which is contained a site descriptor along with various directories
corresponding to the supported document types. Let's take a look at site
descriptor and the examples of the various document types.</p>
-<p>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 <a class="externalLink"
href="http://maven.apache.org/doxia/references/apt-format.html";> APT Format</a>
is available.</p>
+<p>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 <a href="/doxia/references/apt-format.html"> APT
Format</a> is available.</p>
<p>The FML format is the FAQ format.</p>
<p>Other formats are available, but at this point these 3 are the best tested.
There are also several possible output formats, but as of 2.0, only XHTML is
available.</p>
<p>Note that all of the above is optional - just one index file is required in
one of the input trees. Each of the paths will be merged together to form the
root directory of the site.</p></div>
<div class="section">
<h3><a name="Customizing_the_Look_.26_Feel"></a>Customizing the Look &
Feel</h3>
-<p>If you want to tune the way your site looks, you can use a custom skin to
provide your own CSS styles. If that is still not enough, you can even tweak
the output templates that Maven uses to generate the site documentation. You
can visit the <a class="externalLink"
href="http://maven.apache.org/skins/";>Skins site</a> to have a look at some of
the skins that you can use to change the look of your site.</p></div>
+<p>If you want to tune the way your site looks, you can use a custom skin to
provide your own CSS styles. If that is still not enough, you can even tweak
the output templates that Maven uses to generate the site documentation. You
can visit the <a href="/skins/">Skins site</a> to have a look at some of the
skins that you can use to change the look of your site.</p></div>
<div class="section">
<h3><a name="Generating_the_Site"></a>Generating the Site</h3>
<p>Generating the site is very simple, and fast!</p>
@@ -234,7 +234,7 @@ Jason van Zyl" />
</body>
</project></pre></div>
<p><b>Note:</b> The <tt><menu ref="reports"/></tt> element
above. When building the site, this is replaced by a menu with links to all the
reports that you have configured.</p>
-<p>More information about the site descriptor is available at the site for the
<a class="externalLink"
href="http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html";>Maven
Site Plugin</a>.</p></div>
+<p>More information about the site descriptor is available at the site for the
<a href="/plugins/maven-site-plugin/examples/sitedescriptor.html">Maven Site
Plugin</a>.</p></div>
<div class="section">
<h3><a name="Adding_Extra_Resources"></a>Adding Extra Resources</h3>
<p>You can add any arbitrary resource to your site by including them in a
<tt>resources</tt> directory as shown below. Additional CSS files will be
picked up when they are placed in the <tt>css</tt> directory within the
<tt>resources</tt> directory.</p>
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html
(original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html
Sun Apr 15 14:23:11 2018
@@ -147,7 +147,7 @@
<p>This functionality is inspired by the <a class="externalLink"
href="http://www.atlassian.com/software/confluence/";>Confluence</a> snippet
macro, and is provided by the Maven Doxia project by way of the Maven Site
Plugin.</p>
<p>To include snippets of source code in your documentation, first add
comments in the source document surrounding the lines you want to include, and
then refer to the snippet by its id in the documentation file. Each snippet
must be assigned an id, and the id must be unique within the source document.
The id parameter is not required if you want to include the entire file.</p>
<p>Following are examples of snippets in various source documents, as well as
the corresponding macros in the APT documentation format.</p>
-<p>See the Doxia <a class="externalLink"
href="http://maven.apache.org/doxia/macros/index.html#Snippet_Macro";>Macros
Guide</a> for more information and examples.</p>
+<p>See the Doxia <a href="/doxia/macros/index.html#Snippet_Macro">Macros
Guide</a> for more information and examples.</p>
<div class="section">
<h3><a name="Snippets_in_Sources"></a>Snippets in Sources</h3>
<div class="section">
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified:
websites/staging/maven/trunk/content/plugin-developers/common-bugs.html
==============================================================================
--- websites/staging/maven/trunk/content/plugin-developers/common-bugs.html
(original)
+++ websites/staging/maven/trunk/content/plugin-developers/common-bugs.html Sun
Apr 15 14:23:11 2018
@@ -237,7 +237,7 @@ if ( "info".equals( debugLevel
String value = System.getProperty( "maven.test.skip" );
}
}</pre></div>
-<p>The problem is that the properties managed by the <tt>System</tt> class are
global, i.e. shared among all threads in the current JVM. To prevent conflicts
with other code running in the same JVM, Maven plugins should instead query the
execution properties. These can be obtained from <tt><a class="externalLink"
href="http://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/execution/MavenSession.html#getExecutionProperties()">MavenSession.getExecutionProperties()</a></tt>.</p></div>
+<p>The problem is that the properties managed by the <tt>System</tt> class are
global, i.e. shared among all threads in the current JVM. To prevent conflicts
with other code running in the same JVM, Maven plugins should instead query the
execution properties. These can be obtained from <tt><a class="externalLink"
href="https://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/execution/MavenSession.html#getExecutionProperties()">MavenSession.getExecutionProperties()</a></tt>.</p></div>
<div class="section">
<h3><a name="Using_Shutdown_Hooks">Using Shutdown Hooks</a></h3>
<p>People occasionally employ shutdown hooks to perform cleanup tasks, e.g. to
delete temporary files as shown in the example below:</p>
Modified: websites/staging/maven/trunk/content/pom.html
==============================================================================
--- websites/staging/maven/trunk/content/pom.html (original)
+++ websites/staging/maven/trunk/content/pom.html Sun Apr 15 14:23:11 2018
@@ -206,7 +206,7 @@ Karl Heinz Marbaise" />
<div class="section">
<h2><a name="Introduction">Introduction</a></h2>
<ul>
-<li><a class="externalLink"
href="http://maven.apache.org/xsd/maven-4.0.0.xsd";>The POM 4.0.0 XSD</a> and <a
class="externalLink"
href="http://maven.apache.org/ref/current/maven-model/maven.html";>descriptor
reference documentation</a></li></ul>
+<li><a href="/xsd/maven-4.0.0.xsd">The POM 4.0.0 XSD</a> and <a
href="/ref/current/maven-model/maven.html">descriptor reference
documentation</a></li></ul>
<div class="section">
<h3><a name="What_is_the_POM.3F"></a><a name="What_is_the_POM">What is the
POM?</a></h3>
<p>POM stands for "Project Object Model". It is an XML
representation of a Maven project held in a file named <tt>pom.xml</tt>. When
in the presence of Maven folks, speaking of a project is speaking in the
philosophical sense, beyond a mere collection of files containing code. A
project contains configuration files, as well as the developers involved and
the roles they play, the defect tracking system, the organization and licenses,
the URL of where the project lives, the project's dependencies, and all of the
other little pieces that come into play to give code life. It is a
one-stop-shop for all things concerning the project. In fact, in the Maven
world, a project need not contain any code at all, merely a
<tt>pom.xml</tt>.</p></div>
