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 ea32043010a Regen for commit bfb2678c82ea44aa33c385cf8e2044840419c557
add 735c0378524 CAMEL-19158: Ensure errors instantiating throwException
classes are propagated to the exchange
add 6a0e3ffb440 CAMEL-19144: camel-catalog - Include information about
existing Camel releases
add b324299ddd1 Regen for commit 6a0e3ffb4402b0c73643aec4d2db6bd080c98cba
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 (ea32043010a)
\
N -- N -- N refs/heads/regen_bot (b324299ddd1)
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/processor/ThrowExceptionProcessor.java | 9 ++---
...> ThrowExceptionUninstantiatableClassTest.java} | 18 +++++----
.../maven/packaging/UpdateCamelReleasesMojo.java | 46 +++++++++++++---------
3 files changed, 41 insertions(+), 32 deletions(-)
copy
core/camel-core/src/test/java/org/apache/camel/processor/{ThrowExceptionTest.java
=> ThrowExceptionUninstantiatableClassTest.java} (76%)
