This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a change to branch quarkus-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard e3877e1 Upgrade to Quarkus 1.7.0 - WIP
add 8a4d3ee Use java.home system property in TrustStoreResource
add 9a933a5 Fixup #1448 Add delay=-1&repeatCount=1 to the command mode
test route to finish faster
add cb53f18 Fix #1426 Dependency parity checks are now done by Quarkus
extension-descriptor mojo
add 29c7e7a Pipe sanitization done by Quarkus tooling
add b173013 Fixup #1468 Intermittent failure of CamelDevModeTest
new cfc050f Upgrade to Quarkus 1.7.0 - WIP
new 234e8c2 Fix #1403 quarkus-extension-processor race conditions when
modules are built in parallel
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 (e3877e1)
\
N -- N -- N refs/heads/quarkus-master (234e8c2)
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:
.../camel/quarkus/main/CamelMainRuntime.java | 19 +++---
.../camel/quarkus/test/TrustStoreResource.java | 2 +-
.../apache/camel/quarkus/main/cmd/CamelRoute.java | 2 +-
.../quarkus/maven/UpdateExtensionDocPageMojo.java | 24 +++-----
tooling/scripts/validate-dependencies.groovy | 68 +---------------------
5 files changed, 22 insertions(+), 93 deletions(-)
