This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch fix/CAMEL-24810
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 581fc778a8a4 CAMEL-24810: camel-jbang-mcp -
camel_dependency_for_class: which Maven dependency provides a class, and how to
declare it
discard 07362236bd5f chore: camel-jbang - review fixes: the unknown-library
test uses a package no mapping names, and the classNotFound Javadoc is back on
its method
discard 80dad3dd4283 chore: camel-jbang - the bean class check also reads the
generated third-party known dependencies
discard c416c1abfdab chore: camel-jbang - the bean class check honours the
known dependencies camel run downloads, and says how to declare an unknown one
omit 592872ffcfb7 CAMEL-24809: Address review feedback
omit 093c738288c6 Regen
omit d85c3a7ef7d0 CAMEL-24809: camel-kamelet-main - the third-party known
dependencies are generated from a curated list, versions resolved at build time
omit c2af9b32eed4 CAMEL-24809: camel-kamelet-main - known dependencies
mapped by package for the third-party libraries Camel manages
add a6aaa5d4a866 CAMEL-24817: camel-elasticsearch/camel-opensearch -
metadata hygiene (scroll-keep-alive description, deprecate maxRetryTimeout)
(#26591)
add dbd7b0a9bb93 chore(deps): Bump bytebuddy-version from 1.18.13 to
1.18.14 (#26579)
add c7eaecba6f48 CAMEL-24809: camel-kamelet-main - known dependencies
mapped by package, generated from a curated list
add 23f6a24eb7e3 chore: camel-jbang - the bean class check honours the
known dependencies camel run downloads
add 9d8bb7a3e9bd CAMEL-24810: camel-jbang-mcp -
camel_dependency_for_class: which Maven dependency provides a class, and how to
declare it
add 77045c05a6ca CAMEL-24810: camel-jbang - the known-dependency lookup
states its lazy-init intent and answers nothing without the mapping files
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 (581fc778a8a4)
\
N -- N -- N refs/heads/fix/CAMEL-24810 (77045c05a6ca)
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/catalog/components/elasticsearch.json | 6 ++---
.../camel/catalog/components/opensearch.json | 6 ++---
.../apache/camel/component/es/elasticsearch.json | 6 ++---
.../camel/component/es/ElasticsearchComponent.java | 5 ++++
.../component/es/ElasticsearchConfiguration.java | 9 ++++++-
.../camel/component/es/ElasticsearchConstants.java | 2 +-
.../camel/component/opensearch/opensearch.json | 6 ++---
.../component/opensearch/OpensearchComponent.java | 5 ++++
.../opensearch/OpensearchConfiguration.java | 9 ++++++-
.../component/opensearch/OpensearchConstants.java | 2 +-
.../ROOT/pages/camel-4x-upgrade-guide-4_23.adoc | 9 +++++++
.../dsl/ElasticsearchComponentBuilderFactory.java | 1 +
.../dsl/OpensearchComponentBuilderFactory.java | 1 +
.../dsl/ElasticsearchEndpointBuilderFactory.java | 11 +++++---
.../dsl/OpensearchEndpointBuilderFactory.java | 11 +++++---
.../dsl/jbang/core/commands/ai/BeanRefChecks.java | 29 +++++++++++++++++++---
.../commands/ai/SourceValidatorBeanRefsTest.java | 8 ++++++
parent/pom.xml | 2 +-
18 files changed, 102 insertions(+), 26 deletions(-)
