Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of seijoed@gmail.com designates
 209.85.214.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=PoykoDKCvb4jzWNVKWFq0GXNmTDBjIqmoPkbs4HI+3qmxKbtsjozPdV0xbdIdxijI8
         CkNy2S8DMgmo3MlzzQjtosiD6cMzBCeXjYcolj7hQHBmLKnwHiVeNPRWwWyx2Gje+hjc
         tMJQJKDD13TQGZ2wh40HfiyBehjylJPzS+EFo=
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: [PROPSAL] Release Camel 2.7.1
From: Johan Edstrom <seijoed@gmail.com>
In-Reply-To: <273C4E51-9C08-401E-BA23-31E9130D0F7C@gmail.com>
Date: Mon, 4 Apr 2011 08:58:41 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <341C499A-71E9-4104-AE6E-80A42CF7B76E@gmail.com>
References: <0439AD71-907D-4BD8-8AAF-6EC9F6E5DA4F@gmail.com>
 <4D99D4C1.8040008@die-schneider.net> <4D99D48A.8020906@nanthrax.net>
 <4D99D671.5010901@die-schneider.net>
 <0860BED2-5141-499E-A24D-AF483A20B121@gmail.com>
 <3FFFFE3A-E4FF-43D1-BB67-551B44854AE0@gmail.com>
 <273C4E51-9C08-401E-BA23-31E9130D0F7C@gmail.com>
To: dev@camel.apache.org

If cxf:endpoint is tested as is against 2.4.0-SNAPSHOT, i.e the spring =
code, we should be home-free.


On Apr 4, 2011, at 8:56 AM, Hadrian Zbarcea wrote:

> We need to make sure camel-cxf works with both 2.3.x and 2.4.x, =
correct?
> Hadrian
>=20
> On Apr 4, 2011, at 10:49 AM, Johan Edstrom wrote:
>=20
>> 2.4.3 will need some api changes on in/out interceptors.
>> Otherwise an upgrade is  pretty easy.
>>=20
>> Also 2.4 is going to contain plenty more BP stuff.
>> That features file just started working 3 days ago.
>>=20
>> On Apr 4, 2011, at 8:38 AM, Hadrian Zbarcea wrote:
>>=20
>>> Christian, can we get some sort of commitment from the cxf community =
that cxf 2.4.x will be backwards compatible with 2.3.x? I saw that you =
made the following change on trunk:=20
>>> org.apache.cxf.*;version=3D"[2.3.2,2.5)"
>>>=20
>>> Are there any other dependencies we need to upgrade?
>>>=20
>>> Hadrian
>>>=20
>>> On Apr 4, 2011, at 10:32 AM, Christian Schneider wrote:
>>>=20
>>>> Yes we need a new camel release to be compatible with cxf 2.4. The =
question is only if we can also do something with the feature file to =
make it compatible with cxf 2.3 and 2.4.
>>>>=20
>>>> Christian
>>>>=20
>>>>=20
>>>> Am 04.04.2011 16:24, schrieb Jean-Baptiste Onofr=E9:
>>>>> Hi Christian,
>>>>>=20
>>>>> I guess that the camel-cxf POM should be also updated to update =
the CXF version range.
>>>>> So we need a new Camel release for that, no ?
>>>>>=20
>>>>> Regards
>>>>> JB
>>>>>=20
>>>>> On 04/04/2011 04:25 PM, Christian Schneider wrote:
>>>>>> What do we do with the karaf feature file?
>>>>>> The camel-cxf features are not suitable for cxf 2.4. On the other =
hand
>>>>>> CXF 2.4 brings it=B4s own feature file. So if the cxf feature is =
installed
>>>>>> camel-cxf can just be installed.
>>>>>>=20
>>>>>> Any ideas?
>>>>>>=20
>>>>>> Christian
>>>>>>=20
>>>>>>=20
>>>>>> Am 04.04.2011 16:20, schrieb Hadrian Zbarcea:
>>>>>>> Hi,
>>>>>>>=20
>>>>>>> There are a few dependencies that are used with camel that we =
don't
>>>>>>> support as mentioned on the SMX mailing list and CAMEL-3830.
>>>>>>>=20
>>>>>>> I think we should support at least:
>>>>>>> * slf4j 1.6.x
>>>>>>> * jetty 7.3.1.v20110307
>>>>>>> * cxf 2.4.x
>>>>>>> * (if you know of other dependencies that should be upgraded, =
please
>>>>>>> comment)
>>>>>>>=20
>>>>>>> ... and issue a camel-2.7.1 asap. Thoughts?
>>>>>>>=20
>>>>>>> Hadrian
>>>>>>=20
>>>>>=20
>>>>=20
>>>> --=20
>>>> ----
>>>> http://www.liquid-reality.de
>>>>=20
>>>=20
>>=20
>=20