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 2022/09/30 17:55:30 UTC

svn commit: r1904351 - in /maven/website/content: maven-site-1.0-site.jar repositories/artifacts.html repositories/layout.html repositories/metadata.html repositories/remote.html

Author: svn-site-role
Date: Fri Sep 30 17:55:29 2022
New Revision: 1904351

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/maven-site-1.0-site.jar
    maven/website/content/repositories/artifacts.html
    maven/website/content/repositories/layout.html
    maven/website/content/repositories/metadata.html
    maven/website/content/repositories/remote.html

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.

Modified: maven/website/content/repositories/artifacts.html
==============================================================================
--- maven/website/content/repositories/artifacts.html (original)
+++ maven/website/content/repositories/artifacts.html Fri Sep 30 17:55:29 2022
@@ -295,7 +295,7 @@ dependencies, plugins and other), maps t
 <p>Maven for dependencies defines type, that describes what that dependency is (should it be added to classpath and
 many other things). Plugins and extensions may define new types, that is usually a must for plugins introducing
 a packaging (lifecycle mapping) by providing <code>ArtifactHandler</code> components with name corresponding to type name.</p>
-<p>Maven Core out of the box defines following types (handled by same named <code>ArtifactHandler</code> components):</p>
+<p>Maven Core out of the box <a href="/ref/current/maven-core/artifact-handlers.html">defines following types (handled by same named <code>ArtifactHandler</code> components)</a>:</p>
 <table border="0" class="table table-striped">
 <thead>
 <tr class="a">

Modified: maven/website/content/repositories/layout.html
==============================================================================
--- maven/website/content/repositories/layout.html (original)
+++ maven/website/content/repositories/layout.html Fri Sep 30 17:55:29 2022
@@ -173,11 +173,11 @@ the files on file paths for consumption
 <tr class="a">
 <td align="left">artifactId</td>
 <td>none</td>
-<td><code>apache-maven</code> -&gt; <code>apache-maven</code></td></tr>
+<td><code>apache-maven</code></td></tr>
 <tr class="b">
 <td align="left">version</td>
 <td>none</td>
-<td><code>3.8.4</code> -&gt; <code>3.8.4</code></td></tr>
+<td><code>3.8.4</code></td></tr>
 <tr class="a">
 <td align="left">baseVersion</td>
 <td>none</td>
@@ -185,20 +185,20 @@ the files on file paths for consumption
 <tr class="b">
 <td align="left">classifier</td>
 <td>none</td>
-<td><code>bin</code> -&gt; <code>bin</code></td></tr>
+<td><code>bin</code></td></tr>
 <tr class="a">
 <td align="left">extension</td>
 <td>none</td>
-<td><code>tar.gz</code> -&gt; <code>tar.gz</code></td></tr></tbody>
+<td><code>tar.gz</code></td></tr></tbody>
 </table>
 
-<p>And using these properties transformed as above we can construct following path (if classifier not present):</p>
+<p>And using these properties transformed as above, we can construct following path (if classifier not present):</p>
 
-<div class="source"><pre class="prettyprint linenums"><code>${groupId}/${artifactId}/${baseVersion}/${artifactId}-${version}.${extension}
+<div class="source"><pre class="prettyprint linenums"><code>${groupId as directory}/${artifactId}/${baseVersion}/${artifactId}-${version}.${extension}
 </code></pre></div>
 <p>or if classifier present:</p>
 
-<div class="source"><pre class="prettyprint linenums"><code>${groupId}/${artifactId}/${baseVersion}/${artifactId}-${version}-${classifier}.${extension}
+<div class="source"><pre class="prettyprint linenums"><code>${groupId as directory}/${artifactId}/${baseVersion}/${artifactId}-${version}-${classifier}.${extension}
 </code></pre></div>
 <p>So the example artifact above noted as GAV:</p>
 

Modified: maven/website/content/repositories/metadata.html
==============================================================================
--- maven/website/content/repositories/metadata.html (original)
+++ maven/website/content/repositories/metadata.html Fri Sep 30 17:55:29 2022
@@ -156,8 +156,10 @@ transparently operated and handled by Ma
 <p>Links:</p>
 <ul>
 
+<li><a href="/ref/current/maven-repository-metadata/">Reference documentation</a></li>
 <li><a href="/xsd/repository-metadata-1.1.0.xsd">XML Schema</a></li>
-<li><a href="https://gitbox.apache.org/repos/asf?p=maven.git;a=blob_plain;f=maven-repository-metadata/src/main/mdo/metadata.mdo;hb=HEAD" class="externalLink">Modello model</a></li>
+<li><a href="https://gitbox.apache.org/repos/asf?p=maven.git;a=blob_plain;f=maven-repository-metadata/src/main/mdo/metadata.mdo;hb=HEAD" class="externalLink">Modello model</a>
+and its <a href="/ref/current/maven-repository-metadata/repository-metadata.html">descriptor documentation</a></li>
 </ul>
 <p>We distinguish 3 different kinds of metadata files (using GAV coordinates):</p>
 <ul>

Modified: maven/website/content/repositories/remote.html
==============================================================================
--- maven/website/content/repositories/remote.html (original)
+++ maven/website/content/repositories/remote.html Fri Sep 30 17:55:29 2022
@@ -186,9 +186,9 @@ will fetch the required files.</p>
 
 <div class="source"><pre class="prettyprint linenums"><code>1.0-SNAPSHOT -&gt; Remote V Level Repository Metadata -&gt; 1.0-YYYYMMDD.HHMMS-X
 </code></pre></div>
-<p>Due this indirection (the real filename of artifact, the version part) is figured from deployed maven repository metadata,
-the snapshot artifacts are moving target: each snapshot deploy as above will deploy new and new metadata, hence, will
-alter this transformation here (Maven will download different and different snapshot artifact).</p>
+<p>Due this indirection (the real filename of artifact, the version part) is figured from deployed Maven repository metadata,
+the snapshot artifacts are moving target: each snapshot deployment as above will deploy new metadata, hence, will
+alter this transformation here (Maven will download different snapshot artifact).</p>
 <p>Note: it is possible to lock down snapshot artifacts, by using timestamped version in version field of a dependency,
 and it will ensure Maven downloads always same artifact (is not moving target anymore), but <strong>Maven will still consider
 that dependency as snapshot</strong>, and all the fine print applies (for example, release plugin will refuse to release such