Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of elakito@gmail.com designates
 209.85.223.169 as permitted sender)
MIME-Version: 1.0
Sender: elakito@gmail.com
In-Reply-To: 
 <CAF8t5Xvuq=g6HE+42pG2g3wSvvTB=Bfw=gw=Wsa20dnw5T8CQA@mail.gmail.com>
References: <20121113112752.5B32323888EA@eris.apache.org>
	<51DB4D1A-E2EE-4235-8162-78F3117CA8D8@apache.org>
	<CAF8t5Xvuq=g6HE+42pG2g3wSvvTB=Bfw=gw=Wsa20dnw5T8CQA@mail.gmail.com>
Date: Wed, 14 Nov 2012 11:59:28 +0100
Message-ID: 
 <CAF8t5XsEL236_5Y-jR2T70Gzqd0kct=_WSBs9=B_E4uyUMNqbg@mail.gmail.com>
Subject: Re: svn commit: r1408682 - /cxf/trunk/parent/pom.xml
From: Aki Yoshida <ay@apache.org>
To: dev@cxf.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

as discussed on #cxf, I reverted the asm version to 3.x in the root
pom and set the right aris and asm version combination in the test
component itself locally to run the Pojosr based tests.

2012/11/13 Aki Yoshida <ay@apache.org>:
> Hi Dan,
> Okay. In that case, we need to look for another workaround.
> The reason for my change was that I wanted to use Pojosr based
> blueprint tests. That mechanism generates the bundle context from the
> jars on the classpath. Camel's trunk started to use Aries 1.0.0 but
> hasn't updated its asm to 4.0. This is causing an issue because aries
> proxy 1.0.0 uses asm's ClassVisitor which was changed from an
> interface in 3.x to an abstract class in 4.0. So using aries 1.0.0
> with asm 3.x leads to ImcompatibleClassChangeError. And since
> camel-cxf pulls cxf, I thought I should change cxf's aries dependency
> to 1.0.0 and asm to 4.0.
>
> So, I don't know what the best options are. Maybe, we need separate
> test-only components that use their own specific versions?
>
> aki
>
>
>
>
> 2012/11/13 Daniel Kulp <dkulp@apache.org>:
>>
>> Aki,
>>
>> I definitely would prefer not doing the ASM update.  4.x is not compatib=
le with 3.x and including 3.x transitively will very likely start breaking =
a bunch of user applications that may be using ASM.     The Aries update is=
 relatively irrelevant as the deps are all marked provided and the version =
range is output as [0.3,2).  ASM isn't provided though and thus is pulled i=
n transitively.
>>
>> Dan
>>
>>
>> On Nov 13, 2012, at 6:27 AM, ay@apache.org wrote:
>>
>>> Author: ay
>>> Date: Tue Nov 13 11:27:51 2012
>>> New Revision: 1408682
>>>
>>> URL: http://svn.apache.org/viewvc?rev=3D1408682&view=3Drev
>>> Log:
>>> [CXF-5632] upgrade to aries 1.0.0
>>>
>>> Modified:
>>>    cxf/trunk/parent/pom.xml
>>>
>>> Modified: cxf/trunk/parent/pom.xml
>>> URL: http://svn.apache.org/viewvc/cxf/trunk/parent/pom.xml?rev=3D140868=
2&r1=3D1408681&r2=3D1408682&view=3Ddiff
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>> --- cxf/trunk/parent/pom.xml (original)
>>> +++ cxf/trunk/parent/pom.xml Tue Nov 13 11:27:51 2012
>>> @@ -55,10 +55,10 @@
>>>         <extra.saaj.dep.version>${cxf.saaj.impl.version}</extra.saaj.de=
p.version>
>>>
>>>         <!-- stuff related to ASM -->
>>> -        <cxf.asm.groupId>asm</cxf.asm.groupId>
>>> +        <cxf.asm.groupId>org.ow2.asm</cxf.asm.groupId>
>>>         <cxf.asm.artifactId>asm</cxf.asm.artifactId>
>>> -        <cxf.asm.version>3.3.1</cxf.asm.version>
>>> -        <cxf.asm.bundle.version>3.3.1_1</cxf.asm.bundle.version>
>>> +        <cxf.asm.version>4.0</cxf.asm.version>
>>> +        <cxf.asm.bundle.version>4.0</cxf.asm.bundle.version>
>>>         <cxf.osgi.asm.version>[2.0,5)</cxf.osgi.asm.version>
>>>
>>>         <!-- OSGi related properties -->
>>> @@ -166,7 +166,7 @@
>>>         <cxf.ehcache.bundle.version>2.5.1_1</cxf.ehcache.bundle.version=
>
>>>
>>>         <!-- various OSGi related versions -->
>>> -        <cxf.aries.version>0.3.1</cxf.aries.version>
>>> +        <cxf.aries.version>1.0.0</cxf.aries.version>
>>>         <cxf.aries.version.range>[0.3,2)</cxf.aries.version.range>
>>>         <cxf.osgi.version>4.2.0</cxf.osgi.version>
>>>         <cxf.karaf.version>2.2.6</cxf.karaf.version>
>>>
>>>
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>