This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch automatic-periodic-sync
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
omit c3b7011a526 [create-pull-request] automated change
add 01b4d9c0a1b [create-pull-request] automated change (#1693)
add d841a19942a feat(micrometer): log metrics on shutdown
add 927a7596aa8 CAMEL-22289: remove starter IT test
add b34b7a3a37d feat(observability): default logging metrics on shutdown
add 69752dd8b79 [create-pull-request] automated change
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 (c3b7011a526)
\
N -- N -- N refs/heads/automatic-periodic-sync (69752dd8b79)
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:
.../springboot/catalog/components/docling.json | 4 ++--
.../src/main/docs/docling.json | 2 +-
.../springboot/DoclingComponentConfiguration.java | 7 ++++--
.../src/main/docs/micrometer.json | 13 ++++++++++
.../metrics/CamelMetricsAutoConfiguration.java | 6 ++++-
.../metrics/CamelMetricsConfiguration.java | 28 +++++++++++++++++++++-
.../main/resources/config/application.properties | 3 +++
.../camel/itest/springboot/CamelServiceIT.java | 28 ----------------------
8 files changed, 56 insertions(+), 35 deletions(-)
delete mode 100644
tests/camel-itest-spring-boot/src/test/java/org/apache/camel/itest/springboot/CamelServiceIT.java
