We provide such kind of version matrix in the release notes, but it's a
good idea to have a wiki page that track this (including the major
versions alignment, Jira ID for the dependency upgrade, etc).
Anyway, for 2.3.0, I'm working on a spring31 feature.
Regards
JB
On 10/09/2012 08:53 AM, Charles Moulliard wrote:
Even if I understand the karaf position I completely agree about Claus's
remark to also have Spring 3.1 for Camel and others projects.
What I would like to propose is that we create for Karaf/ServiceMix
projects a page containing a table of the different software used and have
a roadmap about them. This question is important not only for Spring
framework but also Pax, Aries, Felix, ... which are (re)packaged into
Karaf/ServiceMix
This will avoid that we discover a few days before the publication of a
release that we have miss something
Just my 5€ cents.
On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen <[email protected]> wrote:
On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp <[email protected]> wrote:
On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré <[email protected]>
wrote:
Agree Claus, but Camel is not the only application running on Karaf.
So, we have to think about "others projects" as well.
I have no problem to upgrade to Spring 3.1.x but later (why not imagine
a Karaf 2.4.x for that, it could be a good indicator), and propose both
Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna
test tonight).
I agree with that. I know CXF has had very little testing with Spring
3.1.x. I would definitely prefer keeping on 3.0.7 for Karaf 2.3 and
think about that for 2.4.
I also agree that this is way to close to "release" to flip out a major
component like spring. Maybe a month ago, but not now.
Yeah I can understand the deadline issue as well.
But its a shame that the new shiny Karaf 2.3.0 comes out of the box
with the old Spring 3.0.7 from Dec 2011. And there has not been any
new releases of Spring 3.0.x since.
It would be cool if it was possible to provide an easy way for people
to switch Karaf to offer Spring 3.1.
Maybe that requires to offer a spring31 feature, and an easy way for
people to configure Karaf to use that.
At Camel we have a CI job that tests Camel with Spring 3.1. The
upgrade for Camel has been painless.
Dan
Regards
JB
On 10/08/2012 06:48 PM, Claus Ibsen wrote:
On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré <[email protected]>
wrote:
Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with
Camel
2.10.
Does it make sense to update to Spring 3.1.x (for future Camel version
maybe) ?
Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are
frankly only holding back because of Karaf.
As when people deploy Camel in Karaf they inherit the spring from
Karaf.
People in the community would like to use Spring 3.1.x as its been out
since December 2011.
And its the stable release path where they cut new releases.
Regards
JB
On 10/08/2012 05:55 PM, Claus Ibsen wrote:
On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. <[email protected]>
wrote:
Hi Claus,
From the Karaf 2.3.0 pom file:
<spring.osgi.version>1.2.1</spring.osgi.version>
<spring2.version>2.5.6.SEC03</spring2.version>
<spring.version>3.0.7.RELEASE</spring.version>
Crap I think you guys shoulder consider switching to the 3.1.2
release
of Spring.
As well Jetty 7.6.7, so people have the latest stable release of
these
2 important pieces.
Cheers,
Jamie
On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen <[email protected]>
wrote:
Hi
What Spring version does Karaf 2.3.0 come with out of the box?
3.0.x
or the newer 3.1.x ?
On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. <
[email protected]>
wrote:
I'm always ready!
Cheers,
Jamie
On Mon, Oct 8, 2012 at 5:08 AM, [email protected] <[email protected]>
wrote:
Great, thanks a lot !
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://wwx.talend.com
----- Reply message -----
From: "Andreas Pieber" <[email protected]>
To: <[email protected]>
Subject: Apache Karaf 2.3.0 very close
Date: Mon, Oct 8, 2012 9:17 am
Hey,
On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré <
[email protected]>
wrote:
@Andreas, could you take a look on KARAF-1878 and KARAF-1752
(assigned to
you) ? If you are busy today, I think we can postpone to 2.3.1.
I wanted to keep KARAF-1878 opened for review till tonight; I'll
apply
afterwards. I'll also apply KARAF-1752 then.
Kind regards,
Andreas
Thanks all guys,
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [email protected]
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [email protected]
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
