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 e705300 Regen for commit 1eccac68bd6546d80459d3f100617a1692087f29
add 5c7977b Upgrade to spring rabbitmq 2.4.1
add 26e2cbc CAMEL-17461: camel-spring-rabbtimq - does not use commons-pool
add 05df679 CAMEL-17461: Migrate from commons-pool v1 to v2
add e1b495b CAMEL-17461: Migrate from commons-pool v1 to v2
add c126788 CAMEL-17461: Migrate from commons-pool v1 to v2
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 (e705300)
\
N -- N -- N refs/heads/regen_bot (c126788)
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/camel-dependencies-pom-template.xml | 1 -
components/camel-jms/pom.xml | 1 +
components/camel-spring-rabbitmq/pom.xml | 6 ------
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_15.adoc | 4 ++++
parent/pom.xml | 8 +-------
5 files changed, 6 insertions(+), 14 deletions(-)
