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.
discard c353b2d Regen for commit 324e418b0b4e898054d512fb6e7b7a7a6e24a84f
add ace6761 CAMEL-17143: camel-health - Add success threshold
add a73696f CAMEL-17121: fixed missing reset the Thread's interrupt status
add 03c3b0a Regen for commit a73696fac26abd9681dd3574202b2f52714e4fe7
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 (c353b2d)
\
N -- N -- N refs/heads/regen_bot (03c3b0a)
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:
.../java/org/apache/camel/health/HealthCheck.java | 1 +
.../camel/health/HealthCheckConfiguration.java | 24 ++++++++++++++++
.../apache/camel/impl/health/HealthCheckTest.java | 22 ++++++++++++++-
.../camel/impl/health/AbstractHealthCheck.java | 33 ++++++++++++++++++----
.../impl/health/HealthCheckRegistryRepository.java | 1 +
...althCheckConfigurationPropertiesConfigurer.java | 6 ++++
.../org/apache/camel/main/BaseMainSupport.java | 1 +
.../api/management/mbean/CamelOpenMBeanTypes.java | 6 ++--
.../camel/management/mbean/ManagedCamelHealth.java | 2 ++
.../apache/camel/support/task/BackgroundTask.java | 1 +
.../modules/ROOT/pages/health-check.adoc | 7 ++++-
11 files changed, 94 insertions(+), 10 deletions(-)
