L.S.,

If that's OK for everyone, I'll cut the 4.4.1 release tomorrow (upgrading
the 4.4.x release to Camel 2.8.4 and CXF 2.4.6)

Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/


On Tue, Jan 31, 2012 at 7:20 AM, Jean-Baptiste Onofré <[email protected]>wrote:

> Hi,
>
> ServiceMix 4.4.1 still use Karaf 2.2.x, so blueprint 0.3.x for now (not
> 0.4). Anyway, we are waiting for a Aries Blueprint 0.4.1 on the Karaf side.
>
> Regards
> JB
>
>
> On 01/30/2012 11:19 PM, geaaru wrote:
>
>> Hi,
>>
>> my 2 cent:
>>
>> - I don't know if it is possible but I think that could be a valid
>> improvement resolve issue about use of cxf inside blueprint.xml in offline
>> environment (with default gw configured). Blueprint is more powerfull on
>> osgi instead of spring and currently it is only possible use spring with
>> cxf on production environment where default gw is available but filtered.
>>
>> This problem probably will be resolved with blueprint-0.4.x that isn't
>> yet scheduled for release... So', happy release of smx-4.4.1, at least for
>> me.
>>
>> Bye.
>> G.
>>
>> On Mon Jan 30 2012 09:55:42 PM CET, Gert Vanthienen<gert.vanthienen@**
>> gmail.com <[email protected]>>  wrote:
>>
>>  Jean-Baptiste,
>>>
>>>
>>> For the 4.4.1 release, I think I would prefer to reuse the 2011.02
>>> components set (as well as all the other dependencies) unless there's a
>>> critical issue to fix in there - that way, we can can easily/quickly
>>> deliver a new version of ServiceMix to get people on the latest versions
>>> of Camel 2.8.x and CXF 2.4.x without having to redo the entire release
>>> cycle.
>>>
>>> Other fixes going into the components, utils, ... trunk will be picked up
>>> when we do the Apache ServiceMix 4.5.0 release, which we probably should
>>> start planning that one right after the 4.4.1 release is out.   I was
>>> hoping to be able to include ActiveMQ 5.6.0 but I'll check back with
>>> them on an ETA on that one - if it's too far out, we can always go with
>>> Camel 2.9.x, CXF 2.5.x and ActiveMQ 5.5.1 instead.
>>>
>>> Anyway, this is just my 2 cents here - wdyt?
>>>
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> FuseSource
>>> Web: http://fusesource.com
>>> Blog: 
>>> http://gertvanthienen.**blogspot.com/<http://gertvanthienen.blogspot.com/>
>>>
>>>
>>> On Mon, Jan 30, 2012 at 5:55 PM, Jean-Baptiste Onofré
>>> <[email protected]>wrote:
>>>
>>>  Hi Gert,
>>>>
>>>> I'm gonna make a build/run on my machine and let you know.
>>>> I have a couple of fixes that I would like to add to the components,
>>>> but it's not a big deal or release stopper.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 01/30/2012 05:00 PM, Gert Vanthienen wrote:
>>>>
>>>>  L.S.,
>>>>>
>>>>>
>>>>> Today, the Camel 2.8.4 release was promoted into central repo so I
>>>>> upgraded
>>>>> our features 4.4.x build to CXF 2.4.6 and Camel 2.8.4.   The
>>>>> resulting kits seem to work fine on my machine, with no duplicate
>>>>> features repositories being listed or any other kind of oddities, so
>>>>> I think we're good to go for
>>>>> our ServiceMix 4.4.1 release.   Does anyone have anything else that
>>>>> needs to
>>>>> go into that release?
>>>>>
>>>>> @Jean-Baptiste: I noticed the release issue is currently assigned to
>>>>> you but if you still have your hands full with the bundles release
>>>>> you're doing, I'll gladly help out and cut the features release
>>>>> somewhere in the next few days.
>>>>>
>>>>> P.S. In the process of doing the upgrades, I accidentally created
>>>>> duplicate
>>>>> issues for these upgrades because Jean-Baptiste already created
>>>>> those as well - made a note-to-self to look harder for existing
>>>>> issues next time around ;)
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Gert Vanthienen
>>>>> ------------------------
>>>>> FuseSource
>>>>> Web: http://fusesource.com
>>>>> Blog:
>>>>> http://gertvanthienen.**blogsp**ot.com/ <http://blogspot.com/><
>>>>> http://gertvanthienen.**blogspot.com/<http://gertvanthienen.blogspot.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
>

Reply via email to