This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch fury-fory
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 30f5a9a9236 CAMEL-22183 - camel-fury - Rename Fury to Fory
discard 1794c62dfac CAMEL-22183 - camel-fury - Rename Fury to Fory
discard 8b8c42aa294 CAMEL-22183 - camel-fury - Rename Fury to Fory
add f668f89dbcf CAMEL-22191: camel-resilience4j - Fix recordExceptions
add 84ad832c16d CAMEL-22183 - camel-fury - Rename Fury to Fory
add 02b37646e0c CAMEL-22183 - camel-fury - Rename Fury to Fory
add 5a2ef2451c7 CAMEL-22183 - camel-fury - Rename Fury to Fory
add 727a8182a2b CAMEL-22183 - camel-fury - Rename Fury to Fory
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 (30f5a9a9236)
\
N -- N -- N refs/heads/fury-fory (727a8182a2b)
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:
.../org/apache/camel/catalog/models.properties | 1 -
.../org/apache/camel/catalog/models/fury.json | 22 ----------------------
.../component/resilience4j/ResilienceReifier.java | 1 +
.../org/apache/camel/model/dataformat/fury.json | 22 ----------------------
.../services/org/apache/camel/model.properties | 1 -
5 files changed, 1 insertion(+), 46 deletions(-)
delete mode 100644
catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/fury.json
delete mode 100644
core/camel-core-model/src/generated/resources/META-INF/org/apache/camel/model/dataformat/fury.json
