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

zregvart pushed a change to branch java-10-test
in repository https://gitbox.apache.org/repos/asf/camel.git.


 discard 2ce40e0  CAMEL-12618: Additional dependencies needed on ...
 discard 49e0712  CAMEL-12618: upgrade Groovy Eclipse compiler
 discard 12d0c8a  CAMEL-12618: Use Groovy 3.0.0-SNAPSHOT for gmav...
 discard 485208c  CAMEL-12618: Use fork of maven-plugin-plugin th...
 discard 61fe0ed  CAMEL-12618: Use fork of MVEL that supports Jav...
 discard a7f4a6c  Temporary disable JDK 9 and karaf-itest and spr...
     add 2ebc05c  CAMEL-12742: Upgrade maven wrapper to 0.4.2
     add 22c0873  CAMEL-12742: Fix file permissions
     add 4f7255a  Add more javadoc to ServiceSupport for implementators to know 
that they should override the doXXX methods.
     add f54a2f3  Upgrade netty-tcnative-boringssl-static to version 
2.0.13.Final
     add 808934f  There is already a new release Upgrade 
netty-tcnative-boringssl-static to version 2.0.14.Final
     add 5434c9d  Upgrade JNats to version 2.0.2
     add 15e5072  CAMEL-12605 Added encrypt/decrypt logic for enveloped entities
     add e136c01  Use the same version of Opencensus (0.12.3) used by gRPC 
1.14.0
     add 57b24a4  CAMEL-12728: Fixed wrong component name bug, that caused 
camel-example-rest-producer to fail its test.
     add a0c030f  Regen
     add 1b81b6f  Attempt to fix flaky test on CI
     add f3a5c31  Upgrade RxJava to version 2.2.1
     new 4df70b4  Temporary disable JDK 9 and karaf-itest and spr...
     new c5dedf5  CAMEL-12618: Use fork of MVEL that supports Jav...
     new 53b9231  CAMEL-12618: Use fork of maven-plugin-plugin th...
     new 0cd790f  CAMEL-12618: Use Groovy 3.0.0-SNAPSHOT for gmav...
     new bd21c0e  CAMEL-12618: upgrade Groovy Eclipse compiler
     new bd158b4  CAMEL-12618: Additional dependencies needed on ...

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   (2ce40e0)
            \
             N -- N -- N   refs/heads/java-10-test (bd158b4)

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 6 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:
 .mvn/wrapper/maven-wrapper.jar                     | Bin 48934 -> 48337 bytes
 camel-core/src/main/docs/eips/aggregate-eip.adoc   |   2 +-
 camel-core/src/main/docs/eips/claimCheck-eip.adoc  |   2 +-
 .../main/docs/eips/hystrixConfiguration-eip.adoc   |  14 +--
 .../src/main/docs/eips/idempotentConsumer-eip.adoc |   2 +-
 camel-core/src/main/docs/eips/split-eip.adoc       |   2 +-
 .../apache/camel/component/rest/RestEndpoint.java  |   2 +-
 .../org/apache/camel/support/ServiceSupport.java   |  37 ++++++-
 .../component/seda/SedaBlockWhenFullTest.java      |   5 +-
 .../camel/component/as2/api/AS2ClientManager.java  |  16 +++
 .../component/as2/api/AS2SignedDataGenerator.java  |   1 +
 ...s7Mime.java => ApplicationPkcs7MimeEntity.java} |  39 ++++++--
 .../component/as2/api/entity/EntityParser.java     | 107 +++++++++++++++++++++
 .../camel/component/as2/api/util/AS2Utils.java     |   6 +-
 parent/pom.xml                                     |   8 +-
 pom.xml                                            |  23 ++---
 16 files changed, 226 insertions(+), 40 deletions(-)
 rename 
components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/entity/{ApplicationPkcs7Mime.java
 => ApplicationPkcs7MimeEntity.java} (72%)

Reply via email to