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 68831f6bf26 Regen for commit e01a06e3d2571ffa2a1c1670c89a3437fe4e0e15
     add 9eaab087ec1 CAMEL-19299: camel-console - Add bean registry console
     add 1192c16bacd Regen for commit 9eaab087ec124ab4466a9b64e468e55e76b1a88e

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   (68831f6bf26)
            \
             N -- N -- N   refs/heads/regen_bot (1192c16bacd)

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:
 .../services/org/apache/camel/dev-console}/bean    |  2 +-
 ...opertiesDevConsole.java => BeanDevConsole.java} | 43 ++++++++++------------
 2 files changed, 20 insertions(+), 25 deletions(-)
 copy 
{components/camel-bean/src/generated/resources/META-INF/services/org/apache/camel/language
 => 
core/camel-console/src/generated/resources/META-INF/services/org/apache/camel/dev-console}/bean
 (53%)
 copy 
core/camel-console/src/main/java/org/apache/camel/impl/console/{PropertiesDevConsole.java
 => BeanDevConsole.java} (53%)

Reply via email to