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 30d8f32a48 Add temporary dependency override for JSONata4Java #4294
discard 6c1f5bcd18 Disable DatasonnetIT due to #4284
discard 5f93c44fb1 Disable microprofile-fault-tolerance testing due to #4225
discard 439cce4753 Upgrade Quarkus to 2.15.0.CR1
add 4b2a0cc928 camel-quarkus-catalog - Make it possible to get the camel
version #4301
new 558259d4d0 Upgrade Quarkus to 2.15.0.CR1
new e02d76f941 Disable microprofile-fault-tolerance testing due to #4225
new 0543d35006 Disable DatasonnetIT due to #4284
new 48f4e2aa73 Add temporary dependency override for JSONata4Java #4294
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 (30d8f32a48)
\
N -- N -- N refs/heads/quarkus-main (48f4e2aa73)
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:
.../quarkus/maven/PrepareCatalogQuarkusMojo.java | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
