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 5bd0470e45e Regen for commit 735c0378524065d9f51425e3e979980de11a893d
add 6a0e3ffb440 CAMEL-19144: camel-catalog - Include information about
existing Camel releases
add d5e6fdfdd65 CAMEL-19144: camel-catalog - Include information about
existing Camel releases
add 8ea41639c10 CAMEL-19144: camel-catalog - Include information about
existing Camel releases
add 0a1b8715469 Regen for commit 8ea41639c10bcb94346b648e839a5c848ccaf28c
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 (5bd0470e45e)
\
N -- N -- N refs/heads/regen_bot (0a1b8715469)
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:
.../catalog/releases/camel-quarkus-releases.json | 149 ++++++++++++++++++
.../org/apache/camel/catalog/CamelCatalog.java | 7 +-
.../apache/camel/catalog/DefaultCamelCatalog.java | 13 +-
.../org/apache/camel/catalog/CamelCatalogTest.java | 14 ++
.../endpoint/dsl/AWS2S3EndpointBuilderFactory.java | 171 ++-------------------
.../maven/packaging/UpdateCamelReleasesMojo.java | 46 +++---
6 files changed, 219 insertions(+), 181 deletions(-)
create mode 100644
catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/releases/camel-quarkus-releases.json
