IMHO the plan for Camel 2.9 is to stay on Spring 3.0.x which we have been using all the time. As well the sister Apache projects is using, eg CXF, SMX, Karaf, AMQ etc.
I am pretty sure though Spring is compatible with itself, so you should most likely be able to upgrade and use Spring 3.1 when its released with Camel 2.9.0. The only compelling reason to upgrade to Spring 3.1 would be that it supports Quartz 2.0.x. Spring 3.0.x does not. But that would mean a non backwards compatible upgrade of quartz. Quartz 2.x and 1.x is of course also not binary compatible. And hence a Spring 3.0 -> 3.1 upgrade is not just a drop in replacement of JAR, for end users of Quartz. On Thu, Dec 1, 2011 at 10:09 PM, geemang <martin....@geefamilyusa.com> wrote: > Hi Guys, > > Whats the plan to get onto Spring 3.1? > > I'm a heavy Grails user and Camel routing is core to every app my company > develops on Grails. > > The near pending release of Grails 2.0 (which embeds Spring 3.1) is tracking > the Spring 3.1 release schedule > (http://jira.grails.org/secure/ReleaseNote.jspa?projectId=10020&version=13004 > ) > > I am helping rev the Grails camel plugins ( e.g. > http://www.grails.org/plugin/routing, > http://www.grails.org/plugin/routing-jms) to Grails 2.0 and trying to get in > synch with the latest Camel version release. > > We'd like to to target camel 2.9 but are worried about it's older Spring > 3.06 dependencies. > > I'm hoping we could spure some momentum to get Camel 2.9 to release on > Spring 3.1. Crazy idea??? > > BTW: I'm using Camel 2.8.3 in Grails 2.0RC2 (with the Spring 3.1RC libs) so > far so good. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-9-release-tp5038092p5039933.html > Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
