You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2020/01/16 17:52:57 UTC
svn commit: r1872889 - in /maven/website/content: maven-site-1.0-site.jar
pom.html
Author: svn-site-role
Date: Thu Jan 16 17:52:57 2020
New Revision: 1872889
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 Thu Jan 16 17:52:57 2020
@@ -1233,7 +1233,7 @@ Display parameters as parsed by Maven (i
</project></pre></div></section><section>
<h3><a name="Repositories">Repositories</a></h3>
<p>Repositories are collections of artifacts which adhere to the Maven repository directory layout. In order to be a Maven repository artifact, a POM file must live within the structure <code>$BASE_REPO/groupId/artifactId/version/artifactId-version.pom</code>. <code>$BASE_REPO</code> can be local (file structure) or remote (base URL); the remaining layout will be the same. Repositories exist as a place to collect and store artifacts. Whenever a project has a dependency upon an artifact, Maven will first attempt to use a local copy of the specified artifact. If that artifact does not exist in the local repository, it will then attempt to download from a remote repository. The repository elements within a POM specify those alternate repositories to search.</p>
-<p>The repository is one of the most powerful features of the Maven community. The default central Maven repository lives on <a class="externalLink" href="https://repo.maven.apache.org/maven2/">https://repo.maven.apache.org/maven2/</a>. Another source for artifacts not yet in Central is the Apache snapshots repo.</p>
+<p>The repository is one of the most powerful features of the Maven community. By default Maven searches the central repository at <a class="externalLink" href="https://repo.maven.apache.org/maven2/">https://repo.maven.apache.org/maven2/</a>. Additional repositories can be configured in the pom.xml `repositories` element. </p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -1251,9 +1251,9 @@ Display parameters as parsed by Maven (i
<updatePolicy>never</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
- <id>apacheSnapshots</id>
- <name>Apache Snapshots</name>
- <url>https://repository.apache.org/snapshots/</url>
+ <name>Nexus Snapshots</name>
+ <id>snapshots-repo</id>
+ <url>https://oss.sonatype.org/content/repositories/snapshots</url>
<layout>default</layout>
</repository>
</repositories>
@@ -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 repositories 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 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>
<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"
@@ -1285,12 +1285,12 @@ Display parameters as parsed by Maven (i
...
</project></pre></div>
<ul>
-<li><b>downloadUrl</b>: is the url of the repository from whence another POM may point to in order to grab this POM's artifact. In the simplest terms, we told the POM how to upload it (through repository/url), but from where can the public download it? This element answers that question.</li>
+<li><b>downloadUrl</b>: is the URL of the repository which another POM can point to in order to grab this POM's artifact. In the simplest terms, we told the POM how to upload it (through repository/url), but from where can the public download it? This element answers that question.</li>
<li><b>status</b>: Warning! Like a baby bird in a nest, the status should never be touched by human hands! The reason for this is that Maven will set the status of the project when it is transported out to the repository. Its valid types are as follows.
<ul>
<li><b>none</b>: No special status. This is the default for a POM.</li>
<li><b>converted</b>: The manager of the repository converted this POM from an earlier version to Maven 2.</li>
-<li><b>partner</b>: This could just as easily have been called synched. This means that this artifact has been synched with a partner repository.</li>
+<li><b>partner</b>: This artifact has been synchronized with a partner repository.</li>
<li><b>deployed</b>: By far the most common status, meaning that this artifact was deployed from a Maven 2 or 3 instance. This is what you get when you manually deploy using the command-line deploy phase.</li>
<li><b>verified</b>: This project has been verified, and should be considered finalized.</li></ul></li></ul><section>
<h4><a name="Repository">Repository</a></h4>