This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit dc5ea5ee507 Regen for commit 42f6d20565693e2559d05514774fa2063ba5afc9
add 23c55596f5d CAMEL-18067: camel-jbang - Do not use log for own commands
as logging should be initialized for running Camel
add 28e10442aeb Upgrade Flink to version 1.15.0
add 12cd6ca616f Sync deps
add 63c99b90568 Regen for commit 12cd6ca616f5f82cff16bbef00511d35f97fcf9b
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 (dc5ea5ee507)
\
N -- N -- N refs/heads/regen_bot (63c99b90568)
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 +-
components/camel-flink/pom.xml | 4 +-
.../jbang/core/commands/AbstractInitKamelet.java | 95 ----------------------
.../camel/dsl/jbang/core/commands/Deploy.java | 32 ++++----
.../camel/dsl/jbang/core/commands/Image.java | 23 +++---
.../camel/dsl/jbang/core/commands/Manifest.java | 10 +--
.../dsl/jbang/core/commands/PropertiesHelper.java | 5 +-
.../apache/camel/dsl/jbang/core/commands/Run.java | 33 +++++++-
.../camel/dsl/jbang/core/commands/Undeploy.java | 19 ++---
.../camel/dsl/jbang/core/common/RuntimeUtil.java | 2 -
parent/pom.xml | 2 +-
11 files changed, 71 insertions(+), 156 deletions(-)
delete mode 100644
dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/AbstractInitKamelet.java
