Author: svn-site-role
Date: Fri Apr 12 18:47:14 2024
New Revision: 1916940
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/developers/release/parent-pom-release.html
maven/website/content/maven-site-1.0-site.jar
Modified: maven/website/content/developers/release/parent-pom-release.html
==============================================================================
--- maven/website/content/developers/release/parent-pom-release.html (original)
+++ maven/website/content/developers/release/parent-pom-release.html Fri Apr 12
18:47:14 2024
@@ -163,13 +163,9 @@
|-- apt
| `-- index.apt
`-- site.xml</pre></div>
-<p>And the <code>index.apt</code> page not only contains instructions about
the content of the parent POM, but it maintains a history of POM releases links
and diffs.</p>
-<p>Each specific step is done to maintain <code>site-pom.xml</code> and
<code>index.apt</code> in sync with the release being
released.</p></section><section>
+<p>Specific step is done to maintain <code>site-pom.xml</code> in sync with
the release being released.</p></section><section>
<h2>Stage the release</h2>
-<p>Before staging the release with usual procedure, you need to update
<code>site-pom.xml</code> and <code>index.apt</code> to take the future release
into account:</p>
-<ol style="list-style-type: decimal">
-<li>update <code>site-pom.xml</code> parent POM version to match the version
being released,</li>
-<li>update <code>src/site-docs/index.apt.vm</code>: add a line in the history
of <code>pom.xml</code> for the version being released, referring to the future
git release tag and date.</li></ol>
+<p>Before staging the release with usual procedure, you need to update
<code>site-pom.xml</code> to take the future release into account - update
<code>site-pom.xml</code> parent POM version to match the version being
released,</p>
<p>Once these modifications are done, you can follow <a
href="../website/deploy-component-reference-documentation.html">standard
component documentation staging steps</a>, taking care to use the
<code>site-pom.xml</code> POM, with <code>mvn -f site-pom.xml ...</code>
command, each time the parent POM's site is generated or published.</p>
<p>Then the only difference is with commands to stage the site:</p>
<div class="verbatim">
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
