Author: svn-site-role
Date: Sat Apr 13 14:16:24 2024
New Revision: 1916966
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 Sat Apr 13
14:16:24 2024
@@ -152,28 +152,21 @@
<li><a href="./maven-project-release-procedure.html"> Maven Project Common
Release procedure</a></li></ul>
<p>Note that Parent POMs have particular conventions for managing and
deploying the documentation.</p><section>
<h2>Rationale</h2>
-<p>To be able to publish a documentation for the parent POM without affecting
released <code>pom.xml</code> and <code>site.xml</code>, parent POM projects
have a specific structure, with the addition of <code>site-pom.xml</code> and
<code>src/site-docs</code> to provide <code>mvn -f site-pom.xml site</code>
with useful documentation content:</p>
-<div class="verbatim">
-<pre>|-- pom.xml
-|-- site-pom.xml
-`-- src
- |-- site
- | `-- site.xml
- `-- site-docs
- |-- apt
- | `-- index.apt
- `-- site.xml</pre></div>
-<p>Specific step is done to maintain <code>site-pom.xml</code> in sync with
the release being released.</p></section><section>
+<p>To be able to publish a documentation for the parent POM without affecting
released <code>pom.xml</code> and <code>site.xml</code>, parent POM projects
have a specific module, with the documentations
<code>docs</code>.</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> 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>
+<p>In Maven Apache Parent POM:</p>
+<div class="verbatim">
+<pre>cd target/checkout
+mvn -f docs site
+mvn -f docs scm-publish:publish-scm</pre></div>
+<p>In Maven Projects Parent POM:</p>
<div class="verbatim">
<pre>cd target/checkout
-mvn -f site-pom.xml site
-mvn -f site-pom.xml scm-publish:publish-scm</pre></div></section><section>
+mvn -f docs site site:stage
+mvn -f docs scm-publish:publish-scm</pre></div></section><section>
<h2>Call the vote</h2>
-<p>In the vote, instead of providing links to JIRA, the parent POMs should
include a link to the Git changes since the last release:</p>
+<p>In the vote, additional to providing links to JIRA, the parent POMs should
include a link to the Git changes since the last release:</p>
<div class="verbatim">
<pre>...
Hi,
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
