You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pp...@apache.org on 2021/08/31 11:28:22 UTC
[camel-quarkus] 01/02: Document mvn cq:await-release
-Dcq.version=$VERSION
This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
commit 91ed088766144fdbf294abc3b991b97ca5fc2ebd
Author: Peter Palaga <pp...@redhat.com>
AuthorDate: Tue Aug 31 12:33:30 2021 +0200
Document mvn cq:await-release -Dcq.version=$VERSION
---
.../pages/contributor-guide/release-guide.adoc | 54 ++++++++++++++--------
pom.xml | 2 +-
2 files changed, 37 insertions(+), 19 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index cf64b61..e68013b 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -142,30 +142,27 @@ $ svn add --force .
$ svn commit -m "Apache Camel Quarkus $VERSION released artifacts"
----
-== Create a GitHub release
-
-This will trigger sending a notification to folks watching the Camel Quarkus github repository,
-so it should ideally happen once the newly released artifacts are available on https://repo1.maven.org/maven2/org/apache/camel/quarkus/camel-quarkus-bom/[Maven Central].
+== Upgrade Camel Quarkus in Quarkus Platform
-The following needs to be done:
+You can proceed with upgrading Camel Quarkus in Quarkus Platform
+once the newly released artifacts are available on https://repo1.maven.org/maven2/org/apache/camel/quarkus/camel-quarkus-bom/[Maven Central].
-* Go to https://github.com/apache/camel-quarkus/releases[https://github.com/apache/camel-quarkus/releases].
-* Click the tag you want to promote to a GitHub release
-* Click "Edit Tag" button
-* In the "New release" form:
- * Leave "Release title" empty
- * Add something meaningful to the description, e.g. something like
+[TIP]
+====
+Synchronization between Apache Maven repository and Maven Central may take hours.
+You may find the `await-release` mojo of `cq-maven-plugin` handy if you need to upgrade Camel Quarkus in the Platform as soon as possible:
+
-[source,markdown]
++
+[source,shell]
----
-Check the full [release announcement](https://camel.apache.org/blog/2021/06/camel-quarkus-release-2.0.0/)
+$ cd camel-quarkus
+$ mvn cq:await-release -Dcq.version=$VERSION
----
+
- * Click the green "Publish release" button at the bottom
-
-== Upgrade Camel Quarkus in Quarkus Platform
-
-When: once the newly released artifacts are available on https://repo1.maven.org/maven2/org/apache/camel/quarkus/camel-quarkus-bom/[Maven Central].
+The mojo first lists the artifacts having `groupId` `org.apache.camel.quarkus` and the given `$VERSION`
+from the local Maven repository and then checks that they are available in Maven Central.
+As long as there are unavailable artifacts, the requests are re-tried with a (configurable) delay of 60 seconds.
+====
[INFO]
====
@@ -215,6 +212,27 @@ mvn clean test
+
* If all tests are passing, send a pull request to the Platform
+== Create a GitHub release
+
+This will trigger sending a notification to folks watching the Camel Quarkus github repository,
+so it should ideally happen once the newly released artifacts are available on https://repo1.maven.org/maven2/org/apache/camel/quarkus/camel-quarkus-bom/[Maven Central].
+
+The following needs to be done:
+
+* Go to https://github.com/apache/camel-quarkus/releases[https://github.com/apache/camel-quarkus/releases].
+* Click the tag you want to promote to a GitHub release
+* Click "Edit Tag" button
+* In the "New release" form:
+ * Leave "Release title" empty
+ * Add something meaningful to the description, e.g. something like
++
+[source,markdown]
+----
+Check the full [release announcement](https://camel.apache.org/blog/2021/06/camel-quarkus-release-2.0.0/)
+----
++
+ * Click the green "Publish release" button at the bottom
+
== Further steps
In addition to the above, the following is needed:
diff --git a/pom.xml b/pom.xml
index 7746029..91f0979 100644
--- a/pom.xml
+++ b/pom.xml
@@ -142,7 +142,7 @@
<zt-exec.version>1.11</zt-exec.version>
<!-- Maven plugin versions (keep sorted alphabetically) -->
- <cq-plugin.version>0.38.0</cq-plugin.version>
+ <cq-plugin.version>0.40.0</cq-plugin.version>
<build-helper-maven-plugin.version>3.1.0</build-helper-maven-plugin.version>
<exec-maven-plugin.version>3.0.0</exec-maven-plugin.version>
<formatter-maven-plugin.version>2.11.0</formatter-maven-plugin.version>