Re: [DISCUSS] - Thoughts on Apache Camel 2.18 and towards 3.0

2016-03-25 Thread Claus Ibsen
Hi There was a comment on my blog about the Camel logo Hey Claus; The OpenTSDB project (http://opentsdb.net/) ran an icon design contest on 99designs. People submit designs and others vote. It's a cool system and I imagine you would get a lot of submissions On Wed, Mar 23, 2016 at 11:07 A

Re: [DISCUSS] - Thoughts on Apache Camel 2.18 and towards 3.0

2016-03-25 Thread Claus Ibsen
Hi Antoine Yay sounds good. What do you fancy working with? We got stuff around OSGi such as - upgrading the tests to be karaf 4.x based - drop karaf 2.x - upgrade to OSGi 5.0 Some easier ones would be in the platforms/karaf/features to make karaf 4 the default being used in the validation, cur

Usage of Lambdas in our Maven build (jdk8-lambdas branch)

2016-03-25 Thread Raul Kripalani
There is good news, bad news, and good news again ;-) *Good news:* Now that Camel 2.18 is officially on JDK8, we can use lambdas in our code. Woohoo! *Bad news:* Our current Maven build breaks when doing so. This is what happens: 1. maven-bundle-plugin version 2.3.x cannot parse JDK8 lambdas

Re: [DISCUSS] - Thoughts on Apache Camel 2.18 and towards 3.0

2016-03-25 Thread Antoine Toulme
I’d like to help for this release. Looks like you got a good laundry list already. Where can I help best in that list? > On Mar 23, 2016, at 3:07 AM, Claus Ibsen wrote: > > Hi > > So Camel 2.17 was the last release supporting Java 1.7. > The next Camel 2.18 is requiring Java 1.8. > > Here is

[GitHub] camel pull request: CAMEL-9762 - Add setters on CipherSuitesParame...

2016-03-25 Thread adessaigne
Github user adessaigne closed the pull request at: https://github.com/apache/camel/pull/919 --- 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 e

[GitHub] camel pull request: Fix syntax to correspond to the correct naming...

2016-03-25 Thread apupier
Github user apupier closed the pull request at: https://github.com/apache/camel/pull/918 --- 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 enab

[GitHub] camel pull request: CAMEL-9762 - Add setters on CipherSuitesParame...

2016-03-25 Thread adessaigne
GitHub user adessaigne opened a pull request: https://github.com/apache/camel/pull/919 CAMEL-9762 - Add setters on CipherSuitesParameters and SecureSocketProtocolsParameters Add setters on `CipherSuitesParameters` and `SecureSocketProtocolsParameters` Side note : `SSLConte

[GitHub] camel pull request: Fix syntax to correspond to the correct naming...

2016-03-25 Thread apupier
GitHub user apupier opened a pull request: https://github.com/apache/camel/pull/918 Fix syntax to correspond to the correct naming of contextIdPattern You can merge this pull request into a Git repository by running: $ git pull https://github.com/apupier/camel master Alternat

AW: [DISCUSS] - Thoughts on Apache Camel 2.18 and towards 3.0

2016-03-25 Thread Walzer, Thomas
Regarding Raul´s ideas: Change often frightens people and changing the engine of a work horse (err, I mean work camel) surely frightens me. Maybe I am a worrisome person. I really like to be able to at least look at the moving parts. If you move to Rx/Go/Scala/whatever (right now) you have surel