This is an automated email from the ASF dual-hosted git repository.
robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
The following commit(s) were added to refs/heads/master by this push:
new f2f3ebf70f Stop the version sync running in every child module
f2f3ebf70f is described below
commit f2f3ebf70fcd9626493e2af8687b9cdea90915ab
Author: Robert Lazarski <[email protected]>
AuthorDate: Mon Sep 7 05:49:52 2026 -1000
Stop the version sync running in every child module
preparationGoals runs across the whole reactor, so the inherited execution
resolved ${basedir} to each child and release:prepare died on
modules/resource-bundle/modules/samples/userguide/src/userguide not
existing.
Marked not inherited: children get the goal with no target and do nothing,
and
the rewrite happens once at the root. The release guide also now records
that a
dry run cannot exercise this -- it never replaces pom.xml, so the goal sees
the
SNAPSHOT version and writes it straight back.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
---
pom.xml | 6 ++++++
src/site/markdown/release-process.md | 7 +++++++
2 files changed, 13 insertions(+)
diff --git a/pom.xml b/pom.xml
index d16e8d04f2..e831faad6a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1355,6 +1355,12 @@
</plugin>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
+ <!-- Not inherited: preparationGoals runs across the whole
reactor,
+ and an inherited execution resolves ${basedir} to each
child,
+ so it looked for
modules/resource-bundle/modules/samples/... and
+ failed the release. Children now have the goal with no
target and
+ do nothing; the rewrite happens once, at the root. -->
+ <inherited>false</inherited>
<executions>
<execution>
<!-- Deliberately bound to no phase: an ordinary build
must not
diff --git a/src/site/markdown/release-process.md
b/src/site/markdown/release-process.md
index 685fbb6795..fd05a1d698 100644
--- a/src/site/markdown/release-process.md
+++ b/src/site/markdown/release-process.md
@@ -135,6 +135,13 @@ You may also execute a dry run of the release process: mvn
release:prepare -Ddry
rewrite, and run the goal by hand if you are cutting a release any other
way.
Left unsynced, the shipped samples point at a SNAPSHOT that does not exist.
+ Two things to know about it. The execution is marked
`<inherited>false</inherited>`
+ because `preparationGoals` runs across the whole reactor, and an inherited
copy
+ resolves `${basedir}` to each child module. And a `-DdryRun=true` run does
**not**
+ exercise the rewrite: a dry run never replaces `pom.xml`, so the goal sees
the
+ SNAPSHOT version and writes that back. Only a real `release:prepare`
transforms
+ the poms first, which is why the check above is on the release commit.
+
The same class of problem bites any sample kept out of the reactor:
`swagger-server` sat at `2.0.1-SNAPSHOT` through the whole 2.0.1 cycle
because
of it. It is a reactor module now, which is the preferred fix where the
sample's
