This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch feature/CAMEL-24708-groovy-message
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 7dc6eeea9919 CAMEL-24708: camel-groovy - a message script variable,
the Camel 4 name of request, and a missing property hint that only names
variables the binding has
add 1aeaf6a356d5 CAMEL-24708: camel-jbang - the CLI's own catalog through
the holder idiom instead of a racy volatile check; camel-tooling-model -
serializing an ApiReferenceModel no longer sets the index on its methods
add ee59d22a691e CAMEL-24708: camel-groovy - a message script variable,
the Camel 4 name of request, and a missing property hint that only names
variables the binding has
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 (7dc6eeea9919)
\
N -- N -- N refs/heads/feature/CAMEL-24708-groovy-message
(ee59d22a691e)
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/dsl/jbang/core/commands/ai/CatalogDocs.java | 12 +++++-------
.../main/java/org/apache/camel/tooling/model/JsonMapper.java | 1 -
2 files changed, 5 insertions(+), 8 deletions(-)
