Jean-Baptiste,
No problem at all, if I ever end up being in a rugby practice session, there will probably be a lot more suffering going on afterwards ;) However, I started off this thread by being wrong about the Karaf version we picked up for Apache ServiceMix 4.5.1 and now we're getting confused ourselves about what will end up in the next release. Perhaps it's time to create ourselves a "what goes in which version" page on the website? Regards, Gert Vanthienen On Tue, Apr 30, 2013 at 4:57 PM, Jean-Baptiste Onofré <[email protected]> wrote: > No, that's fine for me, it's just the forgot this point, thanks for the > reminder ;) > > Keep it for SMX 5.0.0 sounds good to me, and now I remember the discussion > ;) > > You know, I should avoid to answer after a rugby practice, my brain suffered > yesterday evening ;) > > Sorry again for the noise. > > Regards > JB > > > On 04/30/2013 04:54 PM, Gert Vanthienen wrote: >> >> Jean-Baptiste, >> >> >> Awesome, sounds like we're almost good to go for 4.5.2 then. I'm >> trying to commit a few of the outstanding fixes and should have some >> time to cut the release on Friday. >> >> For the upgrade to Karaf 2.3.x, we're already doing that for Apache >> ServiceMix 5.0.0. A while ago we had a discussion on whether or not >> to do the same upgrades for 4.x and we ended up reusing features/trunk >> for the 4.5.1 maintenance release and did the Karaf, Camel, CXF and >> ActiveMQ upgrades on the ServiceMix 5 trunk only. >> >> We can revisit that decision obviously, but personally, I would prefer >> to spend more time on getting Apache ServiceMix 5.0.0 ready for >> release. As far as I can tell, all the bits and pieces we need are >> already available - Camel 2.11.0 was the last one we needed, so it >> only be a matter of hardening things and making sure everything works. >> If Karaf 2.3.2 is available by the time we're ready, we should >> obviously upgrade to that one but if it's not out yet, we can always >> add our own etc/config.properties to pick up this Blueprint fix. >> >> >> Wdyt? >> >> Gert Vanthienen >> >> >> On Tue, Apr 30, 2013 at 3:23 PM, Jean-Baptiste Onofré <[email protected]> >> wrote: >>> >>> Oh, you are right Gert. No, the fix is relevant only starting from Karaf >>> 2.3.x. >>> >>> I was thinking that SMX 4.5.x has been upgraded to Karaf 2.3.x, but you >>> are >>> right. >>> >>> I guess that we can prepare SMX 4.6.x powered by Karaf 2.3.x. WDYT ? >>> >>> Regards >>> JB >>> >>> >>> On 04/30/2013 02:29 PM, Gert Vanthienen wrote: >>>> >>>> >>>> L.S., >>>> >>>> >>>> It just occurred to me that Apache ServiceMix 4.5.x is using Karaf >>>> 2.2.x instead of 2.3.x so we can still pick up a new Karaf release if >>>> we want - the vote for the 2.2.11 release has just been closed. Is >>>> this fix also relevant for Karaf 2.2.x (I notice the KARAF issue fixes >>>> it for several Karaf versions, but not for the 2.2.x series)? >>>> >>>> >>>> Regards, >>>> >>>> Gert Vanthienen >>>> >>>> >>>> On Tue, Apr 30, 2013 at 1:57 PM, Jean-Baptiste Onofré <[email protected]> >>>> wrote: >>>>> >>>>> >>>>> Hi Gert, >>>>> >>>>> it sounds good to me. It makes sense to override in config.properties >>>>> in >>>>> ServiceMix and remove it later. >>>>> >>>>> +1 >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> >>>>> On 04/30/2013 01:55 PM, Gert Vanthienen wrote: >>>>>> >>>>>> >>>>>> >>>>>> Hi JB, >>>>>> >>>>>> >>>>>> So this would be to pick up the fix for >>>>>> https://issues.apache.org/jira/browse/KARAF-2273, right? Personally, >>>>>> I would prefer cherry-picking the config property into the ServiceMix >>>>>> codebase and get this release out of the door, I think. >>>>>> >>>>>> We can always remove that property again once we upgrade to Karaf >>>>>> 2.3.2 in the next release of ServiceMix. >>>>>> >>>>>> >>>>>> Regards, >>>>>> >>>>>> Gert Vanthienen >>>>>> >>>>>> >>>>>> On Tue, Apr 30, 2013 at 1:21 PM, Jean-Baptiste Onofré >>>>>> <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Hi Gert, >>>>>>> >>>>>>> it makes sense. If possible, I would: >>>>>>> >>>>>>> - with Karaf 2.3.2 >>>>>>> - or override the etc/config.properties to set blueprint.sync=true >>>>>>> >>>>>>> Regards >>>>>>> JB >>>>>>> >>>>>>> >>>>>>> On 04/30/2013 11:51 AM, Gert Vanthienen wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> L.S., >>>>>>>> >>>>>>>> >>>>>>>> Over the past few weeks, we fixed a major issue for 4.5.1 with >>>>>>>> endorsed Java libraries, cfr. >>>>>>>> https://issues.apache.org/jira/browse/SMX4-1423 >>>>>>>> >>>>>>>> I would like to do another 4.5.x release just to get this fix out: >>>>>>>> this seems like pretty core functionality that's broken now. >>>>>>>> >>>>>>>> There's also a new release for CXF available, but unfortunately >>>>>>>> there's no matching Camel release yet (cfr. >>>>>>>> https://issues.apache.org/jira/browse/KARAF-971) but I guess we can >>>>>>>> always do another release once a matching Camel 2.10.x is available. >>>>>>>> >>>>>>>> >>>>>>>> Wdyt? >>>>>>>> >>>>>>>> Gert Vanthienen >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 >>> >>> >>> >>> -- >>> 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
