This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard 942a260 Temporarily add netty-tcnative-boringssl-static to the BOM to
work around netty-bom issues
discard 365fcb4 Work around cassandraql depending on Quarkus Vert.x
extensions that no longer exist
discard 17717b5 Upgrade Quarkus to 2.3.0.CR1
add 6bcfd5a Fixup 68be716 Allow extending an existing Catalog
add 640971e Remove superfluous
camel-quarkus-integration-tests-support-custom-type-converter dependency from
the direct test
new 5818fa6 Upgrade Quarkus to 2.3.0.CR1
new 33e36eb Work around cassandraql depending on Quarkus Vert.x
extensions that no longer exist
new 168e246 Temporarily add netty-tcnative-boringssl-static to the BOM to
work around netty-bom issues
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 (942a260)
\
N -- N -- N refs/heads/quarkus-main (168e246)
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 3 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:
integration-test-groups/foundation/direct/pom.xml | 4 ----
.../org/apache/camel/quarkus/maven/PrepareCatalogQuarkusMojo.java | 1 +
2 files changed, 1 insertion(+), 4 deletions(-)
