On Feb 3, 2014, at 9:01 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi > > In Camel 2.12 we dropped support for Spring 3.0. But shipped and > tested with Spring 3.1. > > For Camel 2.13 we could drop support for Spring 3.1. And being shipped > and tested with Spring 3.2. This makes sense. CXF is also flipping to Spring 3.2 with 3.0 to cleanup a bunch of the old deprecated API’s. Dan > > One reason would be that if we have spring 3.2 as minimum then we can > use some of the new APIs it has for better controlling > startup|shutdown of Camel in Spring apps. > > One issue logged recently is > https://issues.apache.org/jira/browse/CAMEL-7156 > > Also Spring 3.1 is EOL and SpringSource. So IMHO I think its okay for > us to move on as well. > > Any thoughts? > > > > -- > 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 > Make your Camel applications look hawt, try: http://hawt.io -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
