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 c7089f77e2b Regen for commit 838646711ca8cad2b41cdfdb1b893ea8fce31f04
add 165f7cb3a25 CAMEL-18483: Fix CamelMicroProfileHealthCheckRegistry
registration for routes and consumers health checks when routes are supervised
add ca2025d9208 Regen for commit 165f7cb3a257b95196f8b3795f5b15c1f310c86c
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 (c7089f77e2b)
\
N -- N -- N refs/heads/regen_bot (ca2025d9208)
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-microprofile-health/pom.xml | 5 ++
.../CamelMicroProfileHealthCheckRegistry.java | 27 +++++--
...MicroProfileHealthSupervisedRoutesMainTest.java | 90 ++++++++++++++++++++++
.../health/CamelMicroProfileHealthTestHelper.java | 78 +++++++++++++++++++
.../health/CamelMicroProfileHealthTestSupport.java | 34 ++------
5 files changed, 199 insertions(+), 35 deletions(-)
create mode 100644
components/camel-microprofile/camel-microprofile-health/src/test/java/org/apache/camel/microprofile/health/CamelMicroProfileHealthSupervisedRoutesMainTest.java
create mode 100644
components/camel-microprofile/camel-microprofile-health/src/test/java/org/apache/camel/microprofile/health/CamelMicroProfileHealthTestHelper.java
