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 a47a3b4d98b Regen for commit b7b9d796355aae3ac1e895baf36b80d5c9403dc8
add 0ee230f90a3 CAMEL-17913: camel-kafka - Add isolationLevel option for
consumer
add f07b7be8ab4 Regen for commit 0ee230f90a3dec7dcc44a93bc4ad8223d405c7c2
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 (a47a3b4d98b)
\
N -- N -- N refs/heads/regen_bot (f07b7be8ab4)
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/catalog/components/kafka.json | 2 ++
.../component/kafka/KafkaComponentConfigurer.java | 6 +++++
.../component/kafka/KafkaEndpointConfigurer.java | 6 +++++
.../component/kafka/KafkaEndpointUriFactory.java | 3 ++-
.../org/apache/camel/component/kafka/kafka.json | 2 ++
.../camel/component/kafka/KafkaConfiguration.java | 24 +++++++++++++++--
.../dsl/KafkaComponentBuilderFactory.java | 31 ++++++++++++++++++++++
.../endpoint/dsl/KafkaEndpointBuilderFactory.java | 30 +++++++++++++++++++++
8 files changed, 101 insertions(+), 3 deletions(-)
