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 03c0d212a53 Regen for commit b4a957304b2df8986cfa377283ae5e73a2b6ef45
add c37601ebbf3 Remove duplicate managed dependency
add 3d64915cdc9 Upgrade Infinispan to version 14.0.3.Final
add 6375534f10e Use latest Infinispan image 14.0.3.Final-1 in test-infra
related module
add 95fa9e70edf Use latest Infinispan image 14.0.3.Final-1 in test-infra
related module
add e5ae5d1a7ae Sync deps
add 2b59602de27 Regen for commit e5ae5d1a7aef84a8738dc70745f479e7d386b236
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 (03c0d212a53)
\
N -- N -- N refs/heads/regen_bot (2b59602de27)
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-dependencies/pom.xml | 2 +-
.../remote/InfinispanRemoteProducerIT.java | 2 +-
parent/pom.xml | 2 +-
.../services/InfinispanLocalContainerService.java | 2 +-
.../src/test/resources/infinispan.xml | 123 +++++++++------------
5 files changed, 56 insertions(+), 75 deletions(-)
