This is an automated email from the ASF dual-hosted git repository.
nfilotto pushed a change to branch CAMEL-17945/fix-unstable-hazelcast-test
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 6d5b2e0ba93 Temporary to get a quick feedback
omit 1ca1f9e81e2 CAMEL-17945: Force waiting before checking the asserts of
the mock
add d2d04932284 CAMEL-17948: Force waiting before checking the asserts of
the mock
add d3a53ac4252 CAMEL-17945: Fix the unstable test
HazelcastSedaTransferExchangeTest
add d9b31eb44e4 Temporary to get a quick feedback
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 (6d5b2e0ba93)
\
N -- N -- N refs/heads/CAMEL-17945/fix-unstable-hazelcast-test
(d9b31eb44e4)
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:
.../java/org/apache/camel/component/mock/MockEndpoint.java | 14 +++++---------
1 file changed, 5 insertions(+), 9 deletions(-)
