Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 51848 invoked from network); 4 Apr 2011 16:55:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2011 16:55:59 -0000 Received: (qmail 95115 invoked by uid 500); 4 Apr 2011 16:55:59 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 95080 invoked by uid 500); 4 Apr 2011 16:55:59 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 95072 invoked by uid 99); 4 Apr 2011 16:55:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 16:55:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of seijoed@gmail.com designates 209.85.210.173 as permitted sender) Received: from [209.85.210.173] (HELO mail-iy0-f173.google.com) (209.85.210.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 16:55:53 +0000 Received: by iym10 with SMTP id 10so7263214iym.32 for ; Mon, 04 Apr 2011 09:55:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=xRjEOFPMe+PVV+eZM/N1C8A4o7bO441aLa2ttWq/a/g=; b=Ss16xKb4ARQGG4Ga4wXSZxuBXv03HO5DaoqOyS77oN/q+sTfiPyfRH/NdWBTEj/J4A YzBn0kcuYGtlGGmD9Z/aUoTKZ756i20sRm7QwMdWWfD0VMnPHtSkOEDRBMSR1rt5YcVD UG2f0iz+JwSJLTXcZiNuQZTP3BomKB9Zh1FxI= 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=JBOLWUUkv5CRM9HjRWR+097hwbPyYkhTKC2hIXFFkwoOxPo8ROlEa/0dYKVft2R9JB AADKV5buz0AZdJXWBpDfrS9orKEvMsFGrQ5wvPvpQAEoRIuoMtB43QmeohJQlu7Sc9mD 6Gb5IL/nhSh9Avo99/c2902L/zUH3fEkQtN3A= Received: by 10.42.200.133 with SMTP id ew5mr5890225icb.182.1301936132785; Mon, 04 Apr 2011 09:55:32 -0700 (PDT) Received: from [192.168.15.10] (184-99-249-196.hlrn.qwest.net [184.99.249.196]) by mx.google.com with ESMTPS id mv26sm3861448ibb.11.2011.04.04.09.55.31 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 09:55:31 -0700 (PDT) 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 In-Reply-To: <3F5858F3-9803-42B4-91DB-96A46F736B1A@gmail.com> Date: Mon, 4 Apr 2011 10:55:25 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <429AEF4A-504E-4D37-A5B6-2B0D133AE6A0@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> <341C499A-71E9-4104-AE6E-80A42CF7B76E@gmail.com> <3F5858F3-9803-42B4-91DB-96A46F736B1A@gmail.com> To: dev@camel.apache.org X-Mailer: Apple Mail (2.1082) Major +1 on this! On Apr 4, 2011, at 10:49 AM, Hadrian Zbarcea wrote: > This probably means that we can release camel-2.7.1 before cxf-2.4.0 = is out. Maybe you guys can make the cxf community aware of the camel = changes (well, I guess I could do that too), so that they have a chance = to test. >=20 > I will create a branch off of the camel-2.7.0 tag, start applying = patches and release a snapshot. This way we can not only decide what = patches to put in 2.7.1, but it won't slow down development on trunk. If = you prefer it another way, please shout. >=20 > Cheers, > Hadrian >=20 >=20 > On Apr 4, 2011, at 10:58 AM, Johan Edstrom wrote: >=20 >> If cxf:endpoint is tested as is against 2.4.0-SNAPSHOT, i.e the = spring code, we should be home-free. >>=20 >>=20 >>=20 >> On Apr 4, 2011, at 8:56 AM, Hadrian Zbarcea wrote: >>=20 >>> 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 >>=20 >=20