You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2025/12/08 08:28:19 UTC

(camel) branch it updated (3dbf52ed4288 -> d795d2687424)

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a change to branch it
in repository https://gitbox.apache.org/repos/asf/camel.git


 discard 3dbf52ed4288 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard 8bf837617f9b CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard 0c248da34882 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard e91deb38f2df CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard 8135d28ace20 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
 discard 961d1d64c443 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
 discard 7c7a911d154b CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add c460646263d5 Regen
     add ced18ccf7b82 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 566f51d4762f CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
     add 3cc65b8f9590 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
     add ddabd8239b12 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 19afbcfbb387 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 037bbf1019a0 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add d795d2687424 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger

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   (3dbf52ed4288)
            \
             N -- N -- N   refs/heads/it (d795d2687424)

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/builder/component/ComponentsBuilderFactory.java  | 4 ++--
 .../camel/builder/component/dsl/BraintreeComponentBuilderFactory.java | 2 +-
 .../camel/builder/component/dsl/StripeComponentBuilderFactory.java    | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)