You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sj...@apache.org on 2024/04/13 14:13:39 UTC

(maven-site) branch master updated: [MPOM-483] Update Releasing A Parent POM according to new modules

This is an automated email from the ASF dual-hosted git repository.

sjaranowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 17a633d2 [MPOM-483] Update Releasing A Parent POM according to new modules
17a633d2 is described below

commit 17a633d29751091c01b35abf91229c1af78b321d
Author: Slawomir Jaranowski <s....@gmail.com>
AuthorDate: Sat Apr 13 10:44:38 2024 +0200

    [MPOM-483] Update Releasing A Parent POM according to new modules
---
 .../apt/developers/release/parent-pom-release.apt  | 39 ++++++++--------------
 1 file changed, 13 insertions(+), 26 deletions(-)

diff --git a/content/apt/developers/release/parent-pom-release.apt b/content/apt/developers/release/parent-pom-release.apt
index cb465de8..603c6c54 100644
--- a/content/apt/developers/release/parent-pom-release.apt
+++ b/content/apt/developers/release/parent-pom-release.apt
@@ -36,44 +36,31 @@ Releasing A Parent POM
 * Rationale
 
   To be able to publish a documentation for the parent POM without affecting released <<<pom.xml>>> and <<<site.xml>>>,
-  parent POM projects have a specific structure, with the addition of <<<site-pom.xml>>> and <<<src/site-docs>>>
-  to provide <<<mvn -f site-pom.xml site>>> with useful documentation content:
-
-------
-|-- pom.xml
-|-- site-pom.xml
-`-- src
-    |-- site
-    |   `-- site.xml
-    `-- site-docs
-        |-- apt
-        |   `-- index.apt
-        `-- site.xml
-------
-
-  Specific step is done to maintain <<<site-pom.xml>>>  in sync with the release being released.
+  parent POM projects have a specific module, with the documentations <<<docs>>>.
 
 * Stage the release
 
-  Before staging the release with usual procedure, you need to update <<<site-pom.xml>>> to
-  take the future release into account - update <<<site-pom.xml>>>
-  parent POM version to match the version being released,
+  Then the only difference is with commands to stage the site:
 
-  Once these modifications are done, you can follow {{{../website/deploy-component-reference-documentation.html}standard component documentation staging steps}},
-  taking care to use the <<<site-pom.xml>>> POM, with <<<mvn -f site-pom.xml ...>>> command, each time the parent POM's site is
-  generated or published.
+  In Maven Apache Parent POM:
 
-  Then the only difference is with commands to stage the site:
+--------
+cd target/checkout
+mvn -f docs site
+mvn -f docs scm-publish:publish-scm
+--------
+
+  In Maven Projects Parent POM:
 
 --------
 cd target/checkout
-mvn -f site-pom.xml site
-mvn -f site-pom.xml scm-publish:publish-scm
+mvn -f docs site site:stage
+mvn -f docs scm-publish:publish-scm
 --------
 
 * Call the vote
 
-  In the vote, instead of providing links to JIRA, the parent POMs should include a link to the Git changes since the
+  In the vote, additional to  providing links to JIRA, the parent POMs should include a link to the Git changes since the
   last release:
 
 -------