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

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


 discard 99adef1  CAMEL-15079: PropertyBindingSupport - Add support for 
parameters to factory method
    omit e8683af  Removed unusued code
    omit 29026c6  CAMEL-15082: Fixed camel-bean to set additional bean 
parameters which did not work correctly before.
    omit 468398d  test ssh-key
    omit 3aa9f2b  CAMEL-14801: Add Category field support to @UriEndpoint 
(#3832)
    omit 561b3d8  Sync Properties
    omit 1535557  Upgrade Log4j to version 2.13.3
    omit 04019ee  CAMEL-14996: Updated doc
    omit 4c33206  Polished
    omit 13ed1ce  Fixed CS
    omit baf7db0  Mark lightweight as experimental
    omit 535c708  Camel-Base: Fixed CS
    omit 7449735  Regen after camel-resteasy merged
    omit 53e4fd6  Typo
    omit 31e011b  CAMEL-15078: camel-core - Registry.bind should inject context 
into CamelContextAware beans
    omit 4557769  CAMEL-2983 - camel-resteasy component
     new 9398ec1  CAMEL-2983 - camel-resteasy component
     new ff79f30  CAMEL-15078: camel-core - Registry.bind should inject context 
into CamelContextAware beans
     new 601dd6e  Typo
     new d3a24fa  Regen after camel-resteasy merged
     new bfd04d9  Camel-Base: Fixed CS
     new 5c23400  Mark lightweight as experimental
     new b7a8734  Fixed CS
     new 8b16f22  Polished
     new a02270c  CAMEL-14996: Updated doc
     new ca1378f  Upgrade Log4j to version 2.13.3
     new 9d08a76  Sync Properties
     new 8beff03  CAMEL-14801: Add Category field support to @UriEndpoint 
(#3832)
     new 3f72c51  CAMEL-15082: Fixed camel-bean to set additional bean 
parameters which did not work correctly before.
     new c5c863b  Removed unusued code
     new 54ac46d  CAMEL-15079: PropertyBindingSupport - Add support for 
parameters to factory method

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   (99adef1)
            \
             N -- N -- N   refs/heads/master (54ac46d)

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.

The 15 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

Reply via email to