This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/main by this push:
new 9d2db8c955 Replace references to camel-quarkus-examples
mvnw-for-each.sh script with mvnw in the release guide
9d2db8c955 is described below
commit 9d2db8c9559cd3f6a4a5be0d9dcc1b744cc53a40
Author: James Netherton <[email protected]>
AuthorDate: Tue Jun 9 08:22:31 2026 +0100
Replace references to camel-quarkus-examples mvnw-for-each.sh script with
mvnw in the release guide
---
.../ROOT/pages/contributor-guide/release-guide.adoc | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index 9af81b8b43..1212b1cb27 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -1,6 +1,8 @@
= Apache Camel Quarkus release process
:page-aliases: release-guide.adoc
+NOTE: Unless a Long Term Support (LTS) version of the documentation exists for
your target release version, it is generally better to use the 'next' version
of the documentation.
+
The process is _mutatis mutandis_ the same as for the main Apache Camel
repository - see the
xref:manual::release-guide.adoc[Release guide] page of the Camel documentation.
@@ -425,7 +427,7 @@ NEW_PLATFORM_VERSION=... # E.g. 2.2.0.Final
git fetch upstream
git checkout camel-quarkus-main
git reset --hard upstream/camel-quarkus-main
-mvn org.l2x6.cq:cq-maven-plugin:2.10.0:examples-set-platform
-Dcq.quarkus.platform.version=$NEW_PLATFORM_VERSION
+./mvnw org.l2x6.cq:cq-maven-plugin:2.10.0:examples-set-platform
-Dcq.quarkus.platform.version=$NEW_PLATFORM_VERSION
./refresh-dockerfiles.sh
git add -A
git commit -m "Upgrade to Quarkus Platform $NEW_PLATFORM_VERSION"
@@ -435,7 +437,7 @@ git commit -m "Upgrade to Quarkus Platform
$NEW_PLATFORM_VERSION"
+
[source,shell]
----
-./mvnw-for-each.sh clean verify
+./mvnw clean verify
----
+
* If everything works for you locally, open a PR to merge `camel-quarkus-main`
to `main`
@@ -447,9 +449,9 @@ NEW_CQ_VERSION=... # the recent release of Camel Quarkus;
e.g. 2.2.0
git checkout main
git fetch upstream
git reset --hard upstream/main
-./mvnw-for-each.sh versions:set versions:update-child-modules
-DnewVersion=$NEW_CQ_VERSION
+./mvnw versions:set versions:update-child-modules -DnewVersion=$NEW_CQ_VERSION
# Update version labels in Kubernetes resources
-./mvnw-for-each.sh process-sources
+./mvnw process-sources
git add -A
git commit -m "Tag $NEW_CQ_VERSION"
git tag $NEW_CQ_VERSION
@@ -469,9 +471,9 @@ NEXT_CQ_VERSION=... # The version used in the current Camel
Quarkus main branch
git checkout camel-quarkus-main
git reset --hard main
./mvnw org.l2x6.cq:cq-maven-plugin:2.10.0:examples-set-platform
-Dcq.camel-quarkus.version=${NEXT_CQ_VERSION}-SNAPSHOT
-Dcq.newVersion=${NEXT_CQ_VERSION}-SNAPSHOT
-./mvnw-for-each.sh versions:update-child-modules -N
+./mvnw versions:update-child-modules -N
# Update version labels in Kubernetes resources
-./mvnw-for-each.sh process-sources
+./mvnw process-sources
git add -A
git commit -m "Next is $NEXT_CQ_VERSION"
git push upstream camel-quarkus-main --force-with-lease
