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:21 UTC
[camel-quarkus] branch main updated (67ad8bc -> 88743f1)
This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
from 67ad8bc Fixup 01719a21 Exclude main-unknown-args-ignore test from the list of tests for the platform again
new 91ed088 Document mvn cq:await-release -Dcq.version=$VERSION
new 88743f1 Update AWS2 test README
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../pages/contributor-guide/release-guide.adoc | 54 ++++++++++++++--------
integration-test-groups/aws2/README.adoc | 6 +--
.../aws2/aws2-sqs-sns/README.adoc | 21 ---------
pom.xml | 2 +-
4 files changed, 39 insertions(+), 44 deletions(-)
delete mode 100644 integration-test-groups/aws2/aws2-sqs-sns/README.adoc
[camel-quarkus] 02/02: Update AWS2 test README
Posted by pp...@apache.org.
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 88743f1ad1c7f0ced1979968b52f7827a8af0522
Author: Peter Palaga <pp...@redhat.com>
AuthorDate: Tue Aug 31 12:38:09 2021 +0200
Update AWS2 test README
---
integration-test-groups/aws2/README.adoc | 6 ++----
.../aws2/aws2-sqs-sns/README.adoc | 21 ---------------------
2 files changed, 2 insertions(+), 25 deletions(-)
diff --git a/integration-test-groups/aws2/README.adoc b/integration-test-groups/aws2/README.adoc
index b3d0124..8704d46 100644
--- a/integration-test-groups/aws2/README.adoc
+++ b/integration-test-groups/aws2/README.adoc
@@ -1,10 +1,8 @@
-== AWS 2 isolated integration tests
+= AWS 2 isolated integration tests
=== Localstack
-The tests not impacted by https://github.com/apache/camel-quarkus/issues/2216 are run against Localstack by default.
-
-The tests impacted by https://github.com/apache/camel-quarkus/issues/2216 are ignored by default.
+The tests able to run against Localstack are run against Localstack by default.
The SES test is ignored unless `MAILSLURP_API_KEY` variable is set.
diff --git a/integration-test-groups/aws2/aws2-sqs-sns/README.adoc b/integration-test-groups/aws2/aws2-sqs-sns/README.adoc
deleted file mode 100644
index 3a8dc7a..0000000
--- a/integration-test-groups/aws2/aws2-sqs-sns/README.adoc
+++ /dev/null
@@ -1,21 +0,0 @@
-== AWS 2 SQS integration tests
-
-By default, the tests are skipped because Localstack does not work, see https://github.com/apache/camel-quarkus/issues/2216
-
-To run the tests against the real AWS API, you need to
-
-* Export Your
- https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys[AWS credentials]
- (access key ID and secret access key)
-* Export our preferred
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions[AWS region].
-
-[source,shell]
-----
-export AWS_ACCESS_KEY=<your-access-key-id>
-export AWS_SECRET_KEY=<your-secret-access-key>
-export AWS_REGION=eu-central-1
-----
-
-You may want to `export CAMEL_QUARKUS_START_MOCK_BACKEND=false` to force testing against
-the real AWS API.
\ No newline at end of file
[camel-quarkus] 01/02: Document mvn cq:await-release
-Dcq.version=$VERSION
Posted by pp...@apache.org.
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>