svn commit: r1874372 - in /maven/website/content: guides/mini/guide-relocation.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Sat Feb 22 11:45:43 2020
New Revision: 1874372

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/mini/guide-relocation.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/guides/mini/guide-relocation.html
==============================================================================
--- maven/website/content/guides/mini/guide-relocation.html (original)
+++ maven/website/content/guides/mini/guide-relocation.html Sat Feb 22 11:45:43 2020
@@ -153,11 +153,11 @@
 <h4><a name="Working_on_past_versions"></a>Working on past versions</h4>
 <ol style="list-style-type: decimal">
 <li>Copy all <code>foo</code>-related files from <code>/bar/foo/</code> in your Maven 2 repository to a temporary location.</li>
-<li>Change the groupId to <code>org.bar</code> in all <code>foo</code>-related pom files in the temporary location.</li>
+<li>Change the groupId to <code>org.bar</code> in all <code>foo</code>-related POM files in the temporary location.</li>
 <li>Copy all files from the temporary location to <code>/org/bar/foo/</code> in your Maven 2 repository.</li>
-<li>Create a minimal Maven 2 pom file for every old release of <code>foo</code> in your Maven 2 repository. The pom files only need to include <code>groupId</code>, <code>artifactId</code>, <code>version</code> and the relocation section.
-<p><b>Note:</b> Before you replace your old pom files in <code>/bar/foo/</code> with these minimal pom files, make sure you have made backups!</p>
-<p>The minimal pom file might look like this for version 1.0 of <code>foo</code>:</p>
+<li>Create a minimal Maven 2 POM file for every old release of <code>foo</code> in your Maven 2 repository. The POM files only need to include <code>groupId</code>, <code>artifactId</code>, <code>version</code> and the relocation section.
+<p><b>Note:</b> Before you replace your old POM files in <code>/bar/foo/</code> with these minimal POM files, make sure you have made backups!</p>
+<p>The minimal POM file might look like this for version 1.0 of <code>foo</code>:</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;groupId&gt;bar&lt;/groupId&gt;
@@ -169,13 +169,13 @@
     &lt;/relocation&gt;
   &lt;/distributionManagement&gt;
 &lt;/project&gt;</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 <code>relocation</code> element. For information on which elements are allowed in the <code>relocation</code> 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 <code>/bar/foo/</code> in your Maven 2 repository. If the pom file needs to be signed, do that as well.</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 <code>relocation</code> element. For information on which elements are allowed in the <code>relocation</code> 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 <code>/bar/foo/</code> in your Maven 2 repository. If the POM file needs to be signed, do that as well.</li>
 <li>If your project syncs with Central, you should now initiate that sync. This might happen automatically depending on your projects sync policy.</li></ol>
 <p>Your <code>foo</code>-artifacts are now available to Maven 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></section><section>
 <h4><a name="Releasing_the_next_version"></a>Releasing the next version</h4>
-<p>When the next release of <code>foo</code> is made, you should publish two Maven 2 pom files: first you should publish <code>foo</code>'s POM with the new groupId <code>org.bar</code>.</p>
-<p>Because data in the repository is not supposed to change, Maven doesn't download pom files that it has already downloaded. Therefore you will also need to publish a relocation POM file with the old groupId <code>bar</code> for the new version: this should be a minimal relocation POM (as described in step 4 above), but for the new version of <code>foo</code>.</p>
+<p>When the next release of <code>foo</code> is made, you should publish two Maven 2 POM files: first you should publish <code>foo</code>'s POM with the new groupId <code>org.bar</code>.</p>
+<p>Because data in the repository is not supposed to change, Maven doesn't download POM files that it has already downloaded. Therefore you will also need to publish a relocation POM file with the old groupId <code>bar</code> for the new version: this should be a minimal relocation POM (as described in step 4 above), but for the new version of <code>foo</code>.</p>
 <p>For the release after that, you only need to publish a Maven POM with a groupId of <code>org.bar</code>, since users of the previous version have been informed of the changed groupId.</p></section></section><section>
 <h3><a name="Examples"></a>Examples</h3><section>
 <h4><a name="Apache_Ant"></a>Apache Ant</h4>

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