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 ac26fd6 Regen for commit 50463ba5a98d4cd30fe6737b0249fa807b570fd3
add 625818c Use an existing bean from the registry if a single candidate
of the given type is available, rather than creating a new one (#5709)
add 38195b2 Regen for commit 625818c8820a1b1633e3784db051fe118e71458e
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 (ac26fd6)
\
N -- N -- N refs/heads/regen_bot (38195b2)
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:
.../component/bean/ConstantTypeBeanHolder.java | 8 +++++-
...va => MethodCallByTypeRefExistingBeanTest.java} | 29 +++++++++++++++++-----
2 files changed, 30 insertions(+), 7 deletions(-)
copy
core/camel-core/src/test/java/org/apache/camel/component/bean/{MethodCallRefOrBeanPrefixTest.java
=> MethodCallByTypeRefExistingBeanTest.java} (72%)
