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

Hi So far I got ftp mvel components to fail in the osgi tests. Have not checked why. On Wed, Mar 30, 2016 at 9:24 PM, Raul Kripalani wrote: > Changes are pushed now. First commit with lambdas done too ;-) > > Gotta keep an eye on Jenkins tonight. > > BTW - OSGi Karaf tests were 100% OK. Thanks

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

Hi Sounds good. Btw the camel archetypes in tooling/archetypes need to be changed as well. There is some that builds OSGi projects. It would be better if we build those like we do build Camel itself now. On Wed, Mar 30, 2016 at 9:24 PM, Raul Kripalani wrote: > Changes are pushed now. First co

Camel.2.16.x.notest - Build # 292 - Failure

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

Camel.trunk.notest - Build # 2706 - Failure

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

[GitHub] camel pull request: CAMEL-6132 - Initial version of camel-test-kar...

GitHub user hqstevenson opened a pull request: https://github.com/apache/camel/pull/923 CAMEL-6132 - Initial version of camel-test-karaf This PR provides the structure modifications. The AbstractFeatureTest class used by camel-itest-karaf is now in the camel-test-karaf module, and

Re: Allow httpClient.XXX configuration to be applied to custom HttpClient

Is there a reason for such strict either or approach? Possibly because it provides two ways to achieve the same goal? The reason I ask is because my situation is one in which the HttpClient is customized to remove the Accept-Encoding: gzip header added to all requests because the decoderFactories

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

Thanks Raul - I’ll finish up the PR for https://issues.apache.org/jira/browse/CAMEL-6132 ASAP. The changes in this one also help with the OSGi tests - I think I’ve got it so they don’t leave Karaf instances hanging around anymore. > On Mar 30, 2016, at 1:24 PM, Raul Kripalani wrote: > > C

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

Changes are pushed now. First commit with lambdas done too ;-) Gotta keep an eye on Jenkins tonight. BTW - OSGi Karaf tests were 100% OK. Thanks for the script, Claus. Cheers, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://ab

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

There’s a JIRA to correct this too https://issues.apache.org/jira/browse/CAMEL-4232 > On Mar 30, 2016, at 12:00 PM, Claus Ibsen wrote: > > On Wed, Mar 30, 2016 at 5:12 PM, Raul Kripalani > wrote: >> Yep, today, hopefully. >> >> Faced a few complications with the Came

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

On Wed, Mar 30, 2016 at 5:12 PM, Raul Kripalani wrote: > Yep, today, hopefully. > > Faced a few complications with the Camel Blueprint and Camel Spring > bundles, which were inlining other modules via the bundle plugin. > Yeah there is some ant tasks that copy the source of camel-core-osgi and ca

[GitHub] camel pull request: CAMEL-9778: Remove deprecated GAE component an...

Github user johnpoth closed the pull request at: https://github.com/apache/camel/pull/921 --- 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 ena

[GitHub] camel pull request: CAMEL-9776 : camel-braintree: add uri param to...

GitHub user lburgazzoli opened a pull request: https://github.com/apache/camel/pull/922 CAMEL-9776 : camel-braintree: add uri param to configure advanced opt… …ions You can merge this pull request into a Git repository by running: $ git pull https://github.com/lburgazzoli/a

[GitHub] camel pull request: CAMEL-9778: Remove deprecated GAE component an...

GitHub user johnpoth opened a pull request: https://github.com/apache/camel/pull/921 CAMEL-9778: Remove deprecated GAE component and dependencies I will update the camel website after this requests gets merged. You can merge this pull request into a Git repository by running: $

Re: Allow httpClient.XXX configuration to be applied to custom HttpClient

Yes its either or. You provide a pre configured http client that you have already configured as you want it. Or you do not, and use the httpClient.xxx to configure it in the uri. On Tue, Mar 29, 2016 at 3:42 PM, mluckam wrote: > For the Jetty component, if a httpClient is specified via the uri

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

Yep, today, hopefully. Faced a few complications with the Camel Blueprint and Camel Spring bundles, which were inlining other modules via the bundle plugin. Cheers, Raúl. On 30 Mar 2016 16:06, "Quinn Stevenson" wrote: > Any updates on when this will be merged? I have a couple of PRs I’m > work

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

Any updates on when this will be merged? I have a couple of PRs I’m working on that this effects. > On Mar 29, 2016, at 11:12 AM, Quinn Stevenson > wrote: > > For the JARs that will not be bundles - what do we want in the MANIFEST.MF? > > >> On Mar 29, 2016, at 9:59 AM, Claus Ibsen >

Re: [VOTE] Release Apache Camel 2.15.6

+1 Dan > On Mar 28, 2016, at 6:29 AM, Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 2.15.6, a new patch release > that includes ~37 fixes and improvements. This will be the last > official patch release for the 2.15.x branch. > > Release notes: > https