>> Hi Dan.
>>
>> It's 3.3.1.. I've also forced it as an external jar on the classpath (I'm
>> executing JUnit from Eclipse) but same result...
>>
>
> Hmm, strange. We'll have to do some more details comparisons of
> classpaths. I'll try to do that this eve.
Problem solved.
It was a problem with "cglib". I had both "cglib: 2.1_3 " and "cglib-nodep:
2.2.2" on the classpath due to transitive dependencies.
Excluding the one not used by Isis ("cglib: 2.1_3 ") was just enough.
Thanks!
El 23/07/2013, a las 10:03, Dan Haywood <[email protected]>
escribió:
> On 22 July 2013 16:42, GESCONSULTOR - Óscar Bou <[email protected]>wrote:
>
>> Hi Dan.
>>
>> It's 3.3.1.. I've also forced it as an external jar on the classpath (I'm
>> executing JUnit from Eclipse) but same result...
>>
>
> Hmm, strange. We'll have to do some more details comparisons of
> classpaths. I'll try to do that this eve.
>
>
>
>
>>
>> Remember that at least with JBoss Developer Studio, it's needed to add to
>> the "integtest" module's classpath the hamcrest-core-1.3.jar and
>> hamcrest-library-1.3.jar for avoiding a java security exception when
>> running tests from Eclipse.
>>
>> Curiosity: which dev environment are you using (specially Eclipse version)?
>>
>
> Eclipse Kepler (4.3), JDK 1.6_recent, Maven 3.0.4
>
> Dan
>
>
>
>
>>
>> Thanks,
>>
>> Oscar
>>
>>