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 a6e570859af Regen for commit 027e471fdf8cdea3899dfeb30d41dbbc448e8384
add b0170fddb2e Regen for commit eb0acef79b59e12843bef08c27cd3a352ccd2a42
(#7933)
add f5ca4dbace4 CAMEL-18248: @BeanInject can inject
ProducerTemplate/FluentProducerTemplate/ConsumerTemplate
add ebb9d8cdf8c Regen for commit eb0acef79b59e12843bef08c27cd3a352ccd2a42
(#7934)
add 16f106350c9 camel-hbase: fix deprecation warnings (#7936)
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 (a6e570859af)
\
N -- N -- N refs/heads/regen_bot (16f106350c9)
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/component/hbase/HBaseProducer.java | 4 +--
.../hbase/mapping/CellMappingStrategyFactory.java | 2 +-
.../impl/engine/CamelPostProcessorHelper.java | 27 +++++++++++++++++++
...st.java => BeanInjectProducerTemplateTest.java} | 31 ++++++----------------
4 files changed, 38 insertions(+), 26 deletions(-)
copy
core/camel-core/src/test/java/org/apache/camel/impl/{BeanInjectRouteBuilderTest.java
=> BeanInjectProducerTemplateTest.java} (65%)
