svn commit: r1923454 - /maven/website/content/guides/mini/guide-releasing.html

[sv...@apache.org]

Author: svn-site-role
Date: Wed Jan 29 21:52:15 2025
New Revision: 1923454

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/mini/guide-releasing.html

Modified: maven/website/content/guides/mini/guide-releasing.html
==============================================================================
--- maven/website/content/guides/mini/guide-releasing.html (original)
+++ maven/website/content/guides/mini/guide-releasing.html Wed Jan 29 21:52:15 2025
@@ -290,8 +290,8 @@ checkpoint.checked-in-release-version=OK
 checkpoint.tagged-release=OK
 checkpoint.prepared-release=OK
 checkpoint.check-in-development-version=OK</pre>
-<p>The <i>release.properties</i> file is created while preparing the release. After performing the release the file remains within the project root directory until the maven user deletes it. The <i>release.properties</i> file can be given to any developer within the team and by simply excuting the <code>release:perform</code> goal can create and deploy a new instance of the project artifact time and again.</p>
-<p>During the execution of the <code>release:perform</code> goal the entire maven build lifecycle is executed on the project. The tagged project source code is extracted, compiled, tested, documented and deployed. An instance of the release artifact is deployed to the machine's local repository. An another instance of the release can be deployed to a remote repository by configuring the <i>distributionManagement</i> element within the <i>pom.xml</i> file.</p>
+<p>The <i>release.properties</i> file is created while preparing the release. By default the file gets deleted after a successful release.</p>
+<p>During the execution of the <code>release:perform</code> goal, Maven executes the project's entire build lifecycle. The tagged project source code is extracted, compiled, tested, documented, and deployed. An instance of the release artifact is deployed to the machine's local repository. An another instance of the release can be deployed to a remote repository by configuring the <i>distributionManagement</i> element within the <i>pom.xml</i> file.</p>
 <p>The following is an example of how a distributionManagement element can be configured within a project <i>pom.xml</i> file.</p>
 <pre class="prettyprint linenums"><code>&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;