L.S.,
I'm a bit puzzled by the proposal for a 4.9.0 release using Karaf 2.3.x - I don't say I'm against the idea as such, I'm just trying to understand what we want to achieve with it. In my mind, the first thing we should try is whether or not we actually get a working assembly with Karaf 3.0.x (using the latest SNAPSHOT, for example). If that works, why not do a ServiceMix 5.0.0.EA1 or something like that as soon as Karaf 3.0.1 gets released, so we have an official release out and have something to announce, blog about, ... At least then we can start collecting feedback on the new Karaf 3.0.x based container. Also, we could focus our efforts on updating docs, READMEs, ... to that version instead of working on two different sets of docs. If things really don't work out at all with Karaf 3.0.x, that's a different story - I can see how having a stable ServiceMix 5 "preview" (called 4.9.0 or 5.0.0.BETA or whatever) based on the old Karaf might buy us some time there, but I would keep that as plan B. We can always commit the work done by anyone volunteering to take a stab at the upgrade to Karaf 3 to a branch and work from there. I don't think I'll get around to giving the upgrade a go myself, but I did try some Camel stuff on Karaf 3 yesterday and at least that seemed to work as normal. Any volunteers to give that upgrade a try? Regards, Gert Vanthienen On Sun, Feb 16, 2014 at 2:30 PM, Krzysztof Sobkowiak <[email protected]> wrote: > Hi > > As long as we are going to release the current code base as SMX 4.9, SMX 5 > based on Karaf 3.x is ok for me. > > Regards > Krzysztof > > > On 16.02.2014 14:19, Cristiano Costantini wrote: >> >> Karaf 3 for ServiceMix 5, >> Karaf 2.3.3 or 2.3.4 for ServiceMix 4.9 >> >> >> 2014-02-16 8:10 GMT+01:00 Achim Nierbeck <[email protected]>: >> >>> Hi, >>> >>> As a version 5 suggests a big major change I'd go for karaf 3 also. And >>> use >>> the current base for a 4.9 as already suggested. >>> >>> Regards, Achim >>> >>> sent from mobile device >>> Am 16.02.2014 08:03 schrieb "Filippo Balicchia" <[email protected]>: >>> >>>> For Serviecemix 5 a prefer to use karaf 3.0.* too. >>>> For me is +1 >>>> >>>> Regards >>>> >>>> --Filippo >>>> >>>> >>>> >>>> >>>> >>>> 2014-02-15 23:17 GMT+01:00 Gert Vanthienen <[email protected]>: >>>> >>>>> L.S., >>>>> >>>>> >>>>> In the "Plan for ServiceMix 5" thread, we've seen a few proposals on >>>>> how to deal with the upgrade to Karaf 3. I think this discussion >>>>> definitely merits a thread of its own. >>>>> >>>>> Personally, I would prefer to do a ServiceMix 5 release with Karaf 3 >>>>> if possible, but I'm not sure how stable/unstable this actually is at >>>>> the moment. The 3.0.0 release definitely had a few issues, but a lot >>>>> of them have already been addressed and I think I even saw a 3.0.1 on >>>>> the roadmap for the next few weeks. >>>>> >>>>> If this delay is all it takes to get that upgrade in ServiceMix 5, I >>>>> think we should do that. However, we do not really know big the >>>>> problem is. Perhaps someone could give it a go and try to figure out >>>>> how big of an issue this upgrade is? The effort should definitely not >>>>> be in vain, we can always commit it to another branch and start >>>>> working on a later release there if necessary. Any volunteers? >>>>> >>>>> If we see it will just take a few more weeks to get everything in >>>>> order for a Karaf 3-based release, we can always do a release >>>>> candidate or two to show the world we're actually moving again and to >>>>> get some feedback from the community on where we're headed - that time >>>>> can actually come in quite handy to work on docs, for example. >>>>> However, if the research shows that things will take too long, we >>>>> probably have to come up with a 2.3.x-based release first anyway. >>>>> >>>>> >>>>> Wdyt? >>>>> >>>>> Gert Vanthienen >>>>> > > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect | Technical Architect @ Capgemini > Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center > <http://www.pl.capgemini-sdm.com/> | Wroclaw > e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak
