Re: [VOTE] Apache Camel 2.15.4 (Attempt #2)

+1 I gave it a test with the Camel in Action source code. On Sat, Oct 24, 2015 at 11:44 AM, Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 2.15.4 that has over 40 fixes > and improvements. As recently discussed on the dev mailing

[GitHub] camel pull request: [CAMEL-9113] Upgrade infinispan to 8.0.1.Final

GitHub user jamesnetherton opened a pull request: https://github.com/apache/camel/pull/661 [CAMEL-9113] Upgrade infinispan to 8.0.1.Final This results in camel-infinispan requiring JDK 8 at runtime. So the component documentation will need updating to reflect this. You can merge

Camel.trunk.notest - Build # 2547 - Fixed

The Apache Jenkins build system has built Camel.trunk.notest (build #2547) Status: Fixed Check console output at https://builds.apache.org/job/Camel.trunk.notest/2547/ to view the results.

[GitHub] camel pull request: [CAMEL-9113] Upgrade infinispan to 8.0.1.Final

Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/661 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

data format for MIME-Multipart

Hi, I have written a data format that can convert a Camel message with attachments into a Camel message having a MIME-Multipart message as message body (and no attachments). The use case for this is to enable the user to send attachments over endpoints that do not directly support attachments,

[GitHub] camel pull request: CAMEL-8959: Remove old code from camel-cxf no ...

Github user atoulme closed the pull request at: https://github.com/apache/camel/pull/659 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is