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
discard fbf608b05ca Regen for commit e487506ef99fbe8c1a99fd58850c87d86afe3d55
add bf6d3a0f75f CAMEL-18766: background tasks without maxDuration are
reeschedulable
add a5764537c61 default implementation for run(Predicate, payload) in
BlockingTask
add f7cd5cab832 Refactoring BackgroundTask - made Latch and completed to
members
add 2e3eb27eca2 Regen for commit f7cd5cab83228cd8e7bb77842976d1f9ed6ded43
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 (fbf608b05ca)
\
N -- N -- N refs/heads/regen_bot (2e3eb27eca2)
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:
.../apache/camel/support/task/BackgroundTask.java | 51 +++++-----------------
.../apache/camel/support/task/BlockingTask.java | 4 +-
.../apache/camel/support/task/ForegroundTask.java | 30 -------------
.../task/BackgroundIterationTimeTaskTest.java | 3 +-
4 files changed, 15 insertions(+), 73 deletions(-)
