Author: svn-site-role
Date: Sun Apr 14 20:39:23 2024
New Revision: 1916989
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 Sun Apr 14 20:39:23 2024
@@ -190,7 +190,9 @@
<ul>
<li><a href="#Repository">Repository</a></li>
<li><a href="#Site_Distribution">Site Distribution</a></li>
-<li><a href="#Relocation">Relocation</a></li></ul></li>
+<li><a href="#Relocation">Relocation</a></li>
+<li><a href="#downloadUrl">downloadUrl</a></li>
+<li><a href="#status">status</a></li></ul></li>
<li><a href="#Profiles">Profiles</a>
<ul>
<li><a href="#Activation">Activation</a></li>
@@ -1227,26 +1229,20 @@ Display parameters as parsed by Maven (i
<h2><a id="Plugin_Repositories">Plugin Repositories</a></h2>
<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>
<h2><a id="Distribution_Management">Distribution Management</a></h2>
-<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>
+<p>Distribution management acts precisely as it sounds: it manages the
distribution of the artifact and supporting files generated throughout the
build process.</p>
<div class="verbatim source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd">
...
<distributionManagement>
- ...
- <downloadUrl>http://mojo.codehaus.org/my-project</downloadUrl>
- <status>deployed</status>
+ <repository>...</repository>
+ <snapshotRepository>...<snapshotRepository>
+ <site>...</site>
+ <relocation>...</relocation>
+ <downloadUrl>...</downloadUrl>
+ <status>...</status>
</distributionManagement>
...
-</project></pre></div>
-<ul>
-<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 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>
+</project></pre></div><section>
<h3><a id="Repository">Repository</a></h3>
<p>Whereas the repositories element specifies in the POM the location and
manner in which Maven may download remote artifacts for use by the current
project, distributionManagement specifies where (and how) this project will get
to a remote repository when it is deployed. The repository elements will be
used for snapshot distribution if the snapshotRepository is not defined.</p>
<div class="verbatim source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1310,7 +1306,36 @@ Display parameters as parsed by Maven (i
</distributionManagement>
...
</project></pre></div>
-<p>Projects are not static; they are living things (or dying things, as the
case may be). A common thing that happens as projects grow, is that they are
forced to move to more suitable quarters. For example, when your next wildly
successful open source project moves under the Apache umbrella, it would be
good to give users a heads-up that the project is being renamed to
<code>org.apache:my-project:1.0</code>. Besides specifying the new address, it
is also good form to provide a message explaining
why.</p></section></section><section>
+<p>Projects are not static; they are living things (or dying things, as the
case may be). A common thing that happens as projects grow, is that they are
forced to move to more suitable quarters. For example, when your next wildly
successful open source project moves under the Apache umbrella, it would be
good to give users a heads-up that the project is being renamed to
<code>org.apache:my-project:1.0</code>. Besides specifying the new address, it
is also good form to provide a message explaining why.</p></section><section>
+<h3><a id="downloadUrl">downloadUrl</a></h3>
+<div class="verbatim source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd">
+ ...
+ <distributionManagement>
+ ...
+
<downloadUrl>http://mojo.codehaus.org/my-project/download.html</downloadUrl>
+ </distributionManagement>
+ ...
+</project></pre></div>
+<p><b>downloadUrl</b> is the URL of the project's download page. If not given
users will be referred to the homepage given by url. This is given to assist in
locating artifacts that are not in the repository due to licensing
restrictions. See for example <a class="externalLink"
href="https://issues.apache.org/jira/browse/MNG-2083";>MNG-2083</a> for a
typical workflow.</p></section><section>
+<h3><a id="status">status</a></h3>
+<div class="verbatim source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd">
+ ...
+ <distributionManagement>
+ ...
+ <status>deployed</status>
+ </distributionManagement>
+ ...
+</project></pre></div>
+<p>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. It is described here just
for understanding, but should never be configured in your
<code>pom.xml</code>.</p>
+<p><b>Status</b> valid values are as follows:</p>
+<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 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></section></section><section>
<h2><a id="Profiles">Profiles</a></h2>
<p>A new feature of the POM 4.0 is the ability of a project to change settings
depending on the environment where it is being built. A <code>profile</code>
element contains both an optional activation (a profile trigger) and the set of
changes to be made to the POM if that profile has been activated. For example,
a project built for a test environment may point to a different database than
that of the final deployment. Or dependencies may be pulled from different
repositories based upon the JDK version used. The elements of profiles are as
follows:</p>
<div class="verbatim source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
