I think the mid term solution would be to extract spring out of karaf and deliver it separately. The good thing is that karaf itself has no dependency on spring so it should be possible. The issue will be mainly with the products deployed on karaf that then would have to carefully select the correct spring version. Today many applications just depend on feature spring and give no version range.

Christian

Am 14.10.2012 13:27, schrieb Claus Ibsen:
On Sun, Oct 14, 2012 at 12:55 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
While we could switch to spring 3.1 in karaf 2.4.0 I think we should not do
it in 2.3.1.

The reason is that 2.3.1 will be a bug fix release. So compatibility is the
most important thing in these releases. The idea behind this is that people
who need an important e.g. security fix should be able to update karaf
without having to retest every deployment.
As Spring 3.1 is a minor update not a bugfix update I think the switch
should not go into a bugfix release of karaf.

We do not really have an official policy like this at karaf but it is how I
understand bugfix releases. So what do other think?

Isn't the point with Karaf that people can assemble the container as
they wish/need.
So if people need to use Spring 3.1, then IMHO they should be able to
do this in Karaf 2.3.x also.

Eg as I have said before. Make it easier for people to change the
Karaf container to run with Spring 3.1 out of the box.
Eg if it can be as easy to change some boot feature to say spring31,
instead of spring etc. Or whatever you guys can come up with.



Christian


On 10/14/2012 12:38 PM, Hendy Irawan wrote:
I strongly support Spring 3.1 for future Karaf 2.3.1 :-)

If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can
use "spring30" feature. But I doubt anyone would ever need it (hopefully).

Hendy



--
View this message in context:
http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Reply via email to