This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a change to branch camel-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard 5e6104b Temporary workaround for #2503 Upgrade to minio 8.2.1 in
Camel 3.10 breaks Quarkiverse Minio and MinioClientProducer in our test
discard 156055a Upgrade to Quarkus 2.0.0.Alpha1
new ab15300 Upgrade to Quarkus 2.0.0.Alpha1
new 9410211 Temporary workaround for #2503 Upgrade to minio 8.2.1 in
Camel 3.10 breaks Quarkiverse Minio and MinioClientProducer in our test
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (5e6104b)
\
N -- N -- N refs/heads/camel-main (9410211)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
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:
.../main/java/org/apache/camel/quarkus/core/CamelContextRecorder.java | 2 ++
1 file changed, 2 insertions(+)
