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 3cb1c4d Regen for commit 7dc869ae0e3b6dc151f3d4a3b38b1483d8372202
add 878fafe CAMEL-16357: Camel-splunk define tcpLocalReceiver port (#5217)
add 1216541 Regen for commit 878fafed99b2b7ff048c056314c42cdbe7a0e85a
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 (3cb1c4d)
\
N -- N -- N refs/heads/regen_bot (1216541)
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:
.../apache/camel/catalog/components/splunk.json | 1 +
.../camel/catalog/docs/splunk-component.adoc | 3 +-
.../component/splunk/SplunkEndpointConfigurer.java | 6 ++++
.../component/splunk/SplunkEndpointUriFactory.java | 3 +-
.../org/apache/camel/component/splunk/splunk.json | 1 +
.../src/main/docs/splunk-component.adoc | 3 +-
.../component/splunk/SplunkConfiguration.java | 14 +++++++++
.../camel/component/splunk/SplunkProducer.java | 5 ++++
.../component/splunk/support/TcpDataWriter.java | 26 ++++++++++++++--
.../camel/component/splunk/ProducerTest.java | 32 ++++++++++++++++++++
.../camel/component/splunk/RawProducerTest.java | 1 +
.../endpoint/dsl/SplunkEndpointBuilderFactory.java | 35 ++++++++++++++++++++++
.../modules/ROOT/pages/splunk-component.adoc | 3 +-
13 files changed, 127 insertions(+), 6 deletions(-)
