This is an automated email from the ASF dual-hosted git repository.
nfilotto pushed a change to branch add-incremental-build
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 0147fa9c05c Adapt camel-package-maven-plugin to incremental build
omit 54e2b165501 incremental-build - Upgrade maven daemon to 1.0-m6
omit 53230c0a71d Add an incremental build
add 4ed48cdff23 Camel-Jbang: Upgrade Camel-Kamelets to version 3.20.5
add 61fbfcfc3e4 Upgrade Icu4j to version 73.1
add 76727bfa8b2 Sync deps
add a950ef9c07f Adapt camel-package-maven-plugin to incremental build
(#10265)
add ca63bacf8fa Add an incremental build
add 5baee53c8a2 incremental-build - Upgrade maven daemon to 1.0-m6
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 (0147fa9c05c)
\
N -- N -- N refs/heads/add-incremental-build (5baee53c8a2)
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.
No new revisions were added by this update.
Summary of changes:
camel-dependencies/pom.xml | 2 +-
.../dsl/jbang/core/commands/ExportBaseCommand.java | 2 +-
.../apache/camel/dsl/jbang/core/commands/Init.java | 2 +-
.../jbang/core/commands/catalog/CatalogDoc.java | 2 +-
.../core/commands/catalog/CatalogKamelet.java | 2 +-
.../templates/run-custom-camel-version.tmpl | 2 +-
.../camel-jbang-main/dist/CamelJBang.java | 2 +-
.../src/main/jbang/main/CamelJBang.java | 2 +-
parent/pom.xml | 2 +-
.../camel/maven/packaging/PrepareCatalogMojo.java | 76 ++++++++++++----------
10 files changed, 52 insertions(+), 42 deletions(-)
