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 25b9af5fe1b Regen for commit db40d24f99b150bd5ff1cea56df5877ae72654de
add 53d6bb2f505 Artemis Priority Tests (#9314)
add 62e8c86ba6f Regen for commit 53d6bb2f505e200ae97230c129fb3c4a94624733
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 (25b9af5fe1b)
\
N -- N -- N refs/heads/regen_bot (62e8c86ba6f)
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:
...rrentTest.java => JmsPriorityConsumerTest.java} | 64 +++++++++++-----------
.../component/jms/TwoConsumerOnSameQueueTest.java | 1 +
2 files changed, 33 insertions(+), 32 deletions(-)
copy
components/camel-jms/src/test/java/org/apache/camel/component/jms/{JmsProducerConcurrentTest.java
=> JmsPriorityConsumerTest.java} (50%)
