Author: svn-site-role
Date: Mon Apr 6 12:48:14 2020
New Revision: 1876185
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/maven-site-1.0-site.jar
maven/website/content/pom.html
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: maven/website/content/pom.html
==============================================================================
--- maven/website/content/pom.html (original)
+++ maven/website/content/pom.html Mon Apr 6 12:48:14 2020
@@ -1269,7 +1269,7 @@ Display parameters as parsed by Maven (i
<li><b>checksumPolicy</b>: When Maven deploys files to the repository, it also
deploys corresponding checksum files. Your options are to <code>ignore</code>,
<code>fail</code>, or <code>warn</code> on missing or incorrect checksums.</li>
<li><b>layout</b>: In the above description of repositories, it was mentioned
that they all follow a common layout. This is mostly correct. The layout
introduced with Maven 2 is the default layout for repositories used by Maven
both 2 & 3; however, Maven 1.x had a different layout. Use this element to
specify which if it is <code>default</code> or
<code>legacy</code>.</li></ul></section><section>
<h3><a name="Plugin_Repositories">Plugin Repositories</a></h3>
-<p>Repositories are home to two major types of artifacts. The first are
artifacts that are used as dependencies of other artifacts. These are the
majority of plugins that reside within central. The other type of artifact is
plugins. Maven plugins are themselves a special type of artifact. Because of
this, plugin repositories may be separated from other repositories (although, I
have yet to hear a convincing argument for doing so). In any case, the
structure of the <code>pluginRepositories</code> element block is similar to
the <code>repositories</code> element. The <code>pluginRepository</code>
elements each specify a remote location of where Maven can find new
plugins.</p></section><section>
+<p>Repositories are home to two major types of artifacts. The first are
artifacts that are used as dependencies of other artifacts. These are the
majority of artifacts that reside within central. The other type of artifact is
plugins. Maven plugins are themselves a special type of artifact. Because of
this, plugin repositories may be separated from other repositories (although, I
have yet to hear a convincing argument for doing so). In any case, the
structure of the <code>pluginRepositories</code> element block is similar to
the <code>repositories</code> element. The <code>pluginRepository</code>
elements each specify a remote location of where Maven can find new
plugins.</p></section><section>
<h3><a name="Distribution_Management">Distribution Management</a></h3>
<p>Distribution management acts precisely as it sounds: it manages the
distribution of the artifact and supporting files generated throughout the
build process. Starting with the last elements first:</p>
<div class="source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
