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 81e1ca14502 Regen for commit e99f805334cfd99906923a6a254e211299692189
add e29f43e33d2 (chores) camel-route-parser: removed unused exceptions
add eeaec71bbb0 (chores) camel-jbang: removed unused exceptions
add 32bdb4e66bd (chores) camel-file: removed unused exceptions
add 19cfba18cb9 (chores) camel-ftp: commented actually used exceptions
add 3c011c9cc2e (chores) camel-hashicorp-vault: removed unused exceptions
add e256b0def2f Regen for commit 3c011c9cc2e6d1ba986dadb13e8a5a6c77f7736c
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 (81e1ca14502)
\
N -- N -- N refs/heads/regen_bot (e256b0def2f)
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:
.../org/apache/camel/parser/helper/CamelXmlHelper.java | 2 +-
.../file/strategy/MarkerFileExclusiveReadLockStrategy.java | 14 ++++++++++++--
.../apache/camel/component/file/remote/FtpEndpoint.java | 5 +++++
.../apache/camel/component/file/remote/FtpsEndpoint.java | 3 ---
.../hashicorp/vault/HashicorpVaultPropertiesFunction.java | 7 ++-----
.../java/org/apache/camel/dsl/jbang/core/commands/Run.java | 2 +-
6 files changed, 21 insertions(+), 12 deletions(-)
