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 9ec53d9 Regen for commit c648a6c34a9e53d5fed005d3a9e8ab424b7a1314 add 2ff600f Regen for commit c648a6c34a9e53d5fed005d3a9e8ab424b7a1314 add 3131d46 CAMEL-17479: configuring beans with {{?foo}} supported. Added unit test. add 9d2ffe2 CAMEL-17479: configuring beans with {{?foo}} supported. 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 (9ec53d9) \ N -- N -- N refs/heads/regen_bot (9d2ffe2) 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: ...va => OptionalPropertyPlaceholderBeanTest.java} | 51 ++++++++++++---------- .../camel/support/PropertyBindingSupport.java | 19 +++++++- 2 files changed, 46 insertions(+), 24 deletions(-) copy core/camel-core/src/test/java/org/apache/camel/component/properties/{ComponentResolvePropertyPlaceholdersTest.java => OptionalPropertyPlaceholderBeanTest.java} (51%)