This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch camel-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard baeb3e5497 Disabled [200~DoubleRoutesPerClassTest, see #6492
discard db24e03a15 Generated poms
discard ccf99d8325 Fixed CamelQuarkusTestSupport method for asserting contexts
discard e5906b1cd4 Upgrade Camel to 4.9.0
add 87adb565e5 Bump
io.quarkiverse.amazonservices:quarkus-amazon-services-bom from 2.16.2 to 2.18.1
new e54863b58c Upgrade Camel to 4.9.0
new da41f1cbbb Fixed CamelQuarkusTestSupport method for asserting contexts
new aa7b381778 Generated poms
new 5841e6ec64 Disabled [200~DoubleRoutesPerClassTest, see #6492
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 (baeb3e5497)
\
N -- N -- N refs/heads/camel-main (5841e6ec64)
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 4 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:
pom.xml | 6 +-
poms/bom/src/main/generated/flattened-full-pom.xml | 2552 ++++++++++----------
.../src/main/generated/flattened-reduced-pom.xml | 118 +-
.../generated/flattened-reduced-verbose-pom.xml | 338 +--
4 files changed, 1507 insertions(+), 1507 deletions(-)
