You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2014/02/03 15:01:44 UTC
[DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
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.
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: cibsen@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
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
In the context of this step, the following “old" ticket has been fixed:
https://issues.apache.org/jira/browse/CAMEL-6365
Babak
Claus Ibsen-2 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.
>
> 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:
> cibsen@
> 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
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Drop-Spring-3-1-support-in-Camel-2-13-onwards-tp5746724p5746929.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by David Karlsen <da...@gmail.com>.
Sounds good to me.
And also if one take into consideration moving onto spring 4.x as well:
https://issues.apache.org/jira/browse/CAMEL-7074
2014-02-03 Claus Ibsen <cl...@gmail.com>:
> 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.
>
> 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: cibsen@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
>
--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by Daniel Kulp <dk...@apache.org>.
On Feb 3, 2014, at 9:01 AM, Claus Ibsen <cl...@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: cibsen@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
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by Christian Müller <ch...@gmail.com>.
+1
Christian
On Mon, Feb 3, 2014 at 3:01 PM, Claus Ibsen <cl...@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.
>
> 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: cibsen@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
>
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Logged a ticket to track this
https://issues.apache.org/jira/browse/CAMEL-7165
On Mon, Feb 3, 2014 at 3:01 PM, Claus Ibsen <cl...@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.
>
> 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: cibsen@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
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@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
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by Christian Müller <ch...@gmail.com>.
I dissabled the Jenkis build [1]
[1]
https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.spring3.1/
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 Tue, Feb 4, 2014 at 3:04 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> +1
>
> FYI, about Spring, I'm working on the "new" Spring bundles (both for
> 3.2.7.RELEASE and 4.0.1.RELEASE).
>
> Regards
> JB
>
>
> On 02/03/2014 03:01 PM, Claus Ibsen 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.
>>
>> 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?
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
FYI, about Spring, I'm working on the "new" Spring bundles (both for
3.2.7.RELEASE and 4.0.1.RELEASE).
Regards
JB
On 02/03/2014 03:01 PM, Claus Ibsen 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.
>
> 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?
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com