I totally mean for 2.15 at the earliest! :) On 14 September 2014 13:22, Christian Müller <christian.muel...@gmail.com> 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 container, it > shouldn't be to difficult to use Camel 2.14.0 with Spring 4. > > Best, > 5 > Am 14.09.2014 19:01 schrieb "Matt Sicker" <boa...@gmail.com>: > > > 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 <claus.ib...@gmail.com> wrote: > > > > > 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 > > > <christian.muel...@gmail.com> wrote: > > > > 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 Camel 2.14.0 and do the > Spring 4 > > > > upgrade (4.0.x or 4.1.x) in Camel 2.15.0. > > > > > > > > Best, > > > > Christian > > > > ----------------- > > > > > > > > Software Integration Specialist > > > > > > > > Apache Member > > > > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer > > > > Apache Incubator PMC Member > > > > > > > > https://www.linkedin.com/pub/christian-mueller/11/551/642 > > > > > > > > On Fri, Sep 12, 2014 at 3:47 AM, Willem Jiang < > willem.ji...@gmail.com> > > > > wrote: > > > > > > > >> Hi, > > > >> > > > >> Because spring-test 4.x is not backward compatible, we have to > create > > > >> camel-test-spring and camel-test-spring3 module for spring 4.x and > > > spring > > > >> 3.x. > > > >> > > > >> Current camel default version of Spring is 3.2.x, if not easy for > the > > > user > > > >> who still want to camel-test-spring to upgrade. > > > >> > > > >> So my suggestion is we switch the default version of spring to 4.x, > > and > > > >> ask the user to manage the all the spring dependency in his pom. > > > >> > > > >> Any thought? > > > >> > > > >> > > > >> -- > > > >> Willem Jiang > > > >> > > > >> Red Hat, Inc. > > > >> Web: http://www.redhat.com > > > >> Blog: http://willemjiang.blogspot.com (English) > > > >> http://jnn.iteye.com (Chinese) > > > >> Twitter: willemjiang > > > >> Weibo: 姜宁willem > > > >> > > > >> > > > >> > > > >> > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > Red Hat, Inc. > > > Email: cib...@redhat.com > > > Twitter: davsclaus > > > Blog: http://davsclaus.com > > > Author of Camel in Action: http://www.manning.com/ibsen > > > hawtio: http://hawt.io/ > > > fabric8: http://fabric8.io/ > > > > > > > > > > > -- > > Matt Sicker <boa...@gmail.com> > > > -- Matt Sicker <boa...@gmail.com>
