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 338d678d2c9 Regen for commit f3c4118fcc2cb6d5860e58955f2d8f0cfe3e3b7b
     add 944694b8ace CAMEL-18865: camel-main - Configuring options on beans dot 
vs square style. Dot style should use getter/setter and square should use 
map/list style first.
     add 9edc233e617 Regen for commit 82b8cf1f28252bb7fc26bfd37df6219f3fd46b37 
(#9005)
     add 6f52501acbb CAMEL-18865: camel-main - Configuring options on beans dot 
vs square style. Dot style should use getter/setter and square should use 
map/list style first.

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   (338d678d2c9)
            \
             N -- N -- N   refs/heads/regen_bot (6f52501acbb)

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:
 .../org/apache/camel/main/BaseMainSupport.java     |  2 +-
 .../java/org/apache/camel/main/MainHelper.java     | 10 ++++-----
 .../java/org/apache/camel/main/MainBeansTest.java  | 26 ++++++++++++++++++++++
 3 files changed, 32 insertions(+), 6 deletions(-)

Reply via email to