I also would like to see Spring 3.1 in Karaf 2.4 and Jetty 8 in Karaf 3.
If we need Spring 3.1 we can do an additional feature but I see no
imediate need for Karaf 2.3.
Christian
Am 09.10.2012 17:34, schrieb Achim Nierbeck:
I second Dan on this only one point I'm not with you :)
2) don't do a 2.4 with jetty 8 but get Karaf 3.0 out of the door
instead, we have Jetty 8 Support available there.
regards, Achim
2012/10/9 Daniel Kulp <dk...@apache.org>:
On Oct 9, 2012, at 8:06 AM, Charles Moulliard <ch0...@gmail.com> wrote:
Is it required to deliver Karaf 2.3.0 now or could we postpone it a few
days till we provide Spring 3.1 ?
I don't think Spring 3.1 upgrade is a "few days" thing. And if you go down
that route, why don't we update to Jetty 8.1 which would bring in Servlet 3 support
(which CXF could leverage). Jetty 8 has been out for a long time as well. And if we
do that, we could update………
It's a never ending thing. At this point, we have been testing all the
various projects with Karaf 2.3 running with Spring 3.0.7, Jetty 7.6.x, etc….
We know things are fairly stable with that. If we keep trying to push things
forward, we'll never get it out, or if we do, we won't have the same level of
testing and confidence. I know CXF has not been extensively (or at all)
tested with Spring 3.1. CXF uses spring a LOT more heavily than Camel and we
HAVE run into issues with the various Spring upgrades in the past. I don't
have a lot of confidence with it, and since CXF was just released (artifacts
promoted this morning), it would be several weeks at least before we would
normally get any fixes that may be needed for CXF to work with Spring 3.1.
From a CXF standpoint, I'm actually MORE confident in a Jetty 8.1 upgrade than
I am a Spring 3.1 upgrade as CXF does test with Jetty 8.1 now.
I would suggest:
1) Get 2.3 out ASAP using what we have been testing it with. It's WAY WAY WAY
overdue at this point.
2) Start a process of timed releases like CXF (and to a lesser extent Camel).
Timed releases avoid a lot of the feature creep. If it's there in time,
great. If not, there is always next release. 2.4 could just be 3 months away
with Sping 3.1 (or 3.2), Jetty 8.1, etc… Of course, get a wiki page up that
shows this roadmap so the other projects that use Karaf heavily can plan
accordingly and start testing.
Dan
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
