[VOTE][Result] Release Apache Camel 2.14.0

As the release kit has a SNAPSHOT dependency, this vote is not passed.  I will cut a new release candidate shortly today. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁wille

Best Practice to write Processor

Hello All, Currently in my application we are defining a Processor for a particular functionality to be achieved. For example, we have a webservice based service, we are using CXF to expose a webservice the endpoint. At the start of the route, the "camel:from" is configured as the webservice en

Re: Switch the default Spring version to Spring 4.x

I hit some issues when running the osgi tests, as some spring-xxx component doesn’t setup the version rang for Spring 4.x so it confuse the OSGi platform to wire the spring package for camel-spring.  But from the test report with Spring4 profile enabled, we could declare that Camel 2.14.0 supp

Camel.2.12.x.notest - Build # 151 - Fixed

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

Camel.2.14.x.notest - Build # 2 - Still Failing

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

$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS

The Apache Jenkins build system has built $PROJECT_NAME (build #$BUILD_NUMBER) Status: $BUILD_STATUS Check console output at $BUILD_URL to view the results.

Camel.trunk.notest - Build # 2163 - Failure

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

Re: [1/2] git commit: upgrade CXF 3.0.1 to 3.0.2-SNAPSHOT

You don't have to build CXF 3.0.2-SNAPSHOT by yourself, it's available through our configured repositories (I didn't build it by myself). I can revert the commit tomorrow, if I cannot convince you... Best, Christian Am 14.09.2014 17:49 schrieb "Claus Ibsen" : > Hi > > I would avoid any SNAPSHOT

Re: Switch the default Spring version to Spring 4.x

I totally mean for 2.15 at the earliest! :) On 14 September 2014 13:22, Christian Müller wrote: > Matt, adding 6 new components (lot of work) in last minute? I don't thinks > is a good idea. > Let's do the upgrade in Camel 2.15.0. > And if you are using Camel in standalone or not in in an OSGI c

Re: Switch the default Spring version to Spring 4.x

Matt, adding 6 new components (lot of work) in last minute? I don't thinks is a good idea. Let's do the upgrade in Camel 2.15.0. And if you are using Camel in standalone or not in in an OSGI container, it shouldn't be to difficult to use Camel 2.14.0 with Spring 4. Best, 5 Am 14.09.2014 19:01 schr

Re: Switch the default Spring version to Spring 4.x

Would it be a good idea to create new components for Spring 4 while still having the Spring 3 versions? Similar to the HttpClient component. On 14 September 2014 10:47, Claus Ibsen wrote: > Hi > > Yeah I frankly also had a bit doubt whether the upgrade was a good > idea as the change is last min

Re: [1/2] git commit: upgrade CXF 3.0.1 to 3.0.2-SNAPSHOT

Hi I would avoid any SNAPSHOT dependency as people dont have CXF snapshot available. If you want to run the feature validation then you can manually do the change locally, or add some profile you can enable to change the CXF version to SNAPSHOT. But please keep the CXF version to 3.0.1. On Sun

Re: Switch the default Spring version to Spring 4.x

Hi Yeah I frankly also had a bit doubt whether the upgrade was a good idea as the change is last minute. I have logged a ticket about the change of default and set its target to Camel 2.15. I am +1 on Muellers suggestion. On Sun, Sep 14, 2014 at 3:29 PM, Christian Müller wrote: > Today I chec

Re: Switch the default Spring version to Spring 4.x

Today I checked the current trunk (2.15-SNAPSHOT) and realized that 6 components will not work with Spring 4 nicely at present: - camel-spring-ws - camel-spring-security - camel-spring-redis - camel-spring-integration - camel-spring-batch - camel-olingo2 I suggest to stick to Spring 3.2.x for Came

Re: git commit: expand the Spring version range to include Spring 4.0.x after we set Spring 4 as default

Without this change, the feature validation fails because the Spring version range [3.2,4) doesn't include Spring 4.0.7. RELEASE we are using as default now. Any idea to solve this in a different way? Best, Christian On Sun, Sep 14, 2014 at 12:27 PM, Claus Ibsen wrote: > Hi > > I think this b

Re: git commit: expand the Spring version range to include Spring 4.0.x after we set Spring 4 as default

Hi I think this breaks Camel on karaf/smx. Can you double check and likely revert back. sprin-dm do not support spring 4.x. So when you do like this it install spring 4, and spring-dm fails. We need to keep the range to 3.x. And the karaf/smx guys need to fork spring-dm and fix it so it can suppo

Re: mvn:org.apache.cxf/cxf-tools-common/3.0.1 is not an OSGi bundle

Because this prevents us to validate our feature file, I would like to upgrade trunk (2.15-SNAPSHOT) to CXF 3.0.2-SNAPSHOT exceptionally. Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache In