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 b583be9 Regen for commit 2bd9b1f077fae82f62b25f34f939b58dbae67c03
add b7118b4 camel-core - Resumable DSL keep same type in Java DSL as it
has no mo… (#7134)
add ddf43dc camel-solr use same version of protobuf for testing
add 00175a3 Regen for commit 05323aa9a6094e333a9b7b8e78d918efba018851
add 8436983 CAMEL-17757: camel-hbase - Upgrade to 2.4.10
add 75fe8ec Regen
add 500ed56 Regen for commit 75fe8ecaa90c1103fdca69632a70ee7f72bed124
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 (b583be9)
\
N -- N -- N refs/heads/regen_bot (500ed56)
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-solr/pom.xml | 10 +++++++
.../docs/modules/eips/pages/resume-strategies.adoc | 8 +++---
.../apache/camel/model/ProcessorDefinition.java | 32 +++++++++++++++++-----
.../apache/camel/model/ResumableDefinition.java | 3 ++
.../FileConsumerResumeFromOffsetStrategyTest.java | 5 ++--
.../file/FileConsumerResumeStrategyTest.java | 2 +-
parent/pom.xml | 2 +-
8 files changed, 48 insertions(+), 16 deletions(-)
