You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ja...@apache.org on 2021/03/25 08:23:40 UTC

[camel-quarkus] branch camel-master updated (4ef5ef4 -> edfa1c4)

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

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


 discard 4ef5ef4  Disable doc xref checks as there is no camel-3.9.x branch yet
 discard 77d5155  Add Camel 3.9.0 staging repository
 discard acd0611  Spring RabbitMQ integration test fails in native mode with Camel 3.9.0
 discard babab8d  Splunk native support #1698
 discard 4ce128a  adapt to the latest camel apis
 discard bd62a49  dsl: remove support for the old route definition loader
 discard a1a70c5  dsl: fix findings
 discard 7fb82e8  dsl: regen
 discard 152ebfb  dsl: support for java-joor-dsl
 discard c82f7df  dsl: support for yaml-dsl
 discard 6d6ba36  dsl: support for xml-io-dsl
 discard b678af3  Optaplanner : upgrade to 8.x extension #2243
 discard 2062ff8  Upgrade to Camel 3.9.0
     add 8db1c47  Upgrade to Camel 3.9.0
     add 23df251  Optaplanner : upgrade to 8.x extension #2243
     add 91296f9  dsl: support for xml-io-dsl
     add 6ad200a  dsl: support for yaml-dsl
     add bb65020  dsl: support for java-joor-dsl
     add 9b1bc41  dsl: regen
     add 60d2183  dsl: fix findings
     add 4ba652a  dsl: remove support for the old route definition loader
     add 67761f5  adapt to the latest camel apis
     add 07211db  Splunk native support #1698
     add b1ef713  Spring RabbitMQ integration test fails in native mode with Camel 3.9.0
     add de28081  Add Camel 3.9.0 staging repository
     add 84aeade  Disable doc xref checks as there is no camel-3.9.x branch yet
     add edfa1c4  Regenerate documentation

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   (4ef5ef4)
            \
             N -- N -- N   refs/heads/camel-master (edfa1c4)

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:
 .../reference/{others/zipkin.adoc => components/aws-secrets-manager.adoc} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 copy docs/modules/ROOT/partials/reference/{others/zipkin.adoc => components/aws-secrets-manager.adoc} (100%)