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 f49f069 Regen for commit 65968e8668d4fc17c10df38b45ec7677b706a2d4
add 26960c2 Regen for commit c94de394cc694537e653476fde2ebc6e5d20401e
add b307cac CAMEL-17712: Clear thread local when camel context is stopped.
add 969ce55 Regen for commit b307cac8a9dd4e6c4edc0230ff9f7b7ecf502a7f
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 (f49f069)
\
N -- N -- N refs/heads/regen_bot (969ce55)
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:
.../resources/org/apache/camel/catalog/others.properties | 1 -
.../org/apache/camel/catalog/others/console.json | 15 ---------------
.../java/org/apache/camel/impl/DefaultCamelContext.java | 6 ++++++
3 files changed, 6 insertions(+), 16 deletions(-)
delete mode 100644
catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/others/console.json
