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 a5bb1be5023 Regen for commit 26e2fb08fac6d56ad8e2dee534d8472c637b7605
add e590c3be8d4 Regen for commit 0310e4a6b8aa2a1f63e2b579ab8f1d232586d1a5
add bbd7c363cfc CAMEL-18957: prevent a few NPEs if the context is not
created
add 5ac42a69c1a Regen for commit bbd7c363cfc47fa82e2afc28d95b9bd0033022ba
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 (a5bb1be5023)
\
N -- N -- N refs/heads/regen_bot (5ac42a69c1a)
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:
.../test/infra/core/DefaultCamelContextExtension.java | 3 +++
.../test/infra/core/DefaultContextLifeCycleManager.java | 17 +++++++++++++++--
.../test/infra/core/TransientCamelContextExtension.java | 3 +++
3 files changed, 21 insertions(+), 2 deletions(-)
