I updated the gradle-wrapper.properties file and run "gradlew wrapper"
command.
Then "gradlew test" and unfortunately got the same error.

Vaclav



On Wed, Jun 2, 2010 at 11:54 AM, Adam Murdoch <[email protected]> wrote:

>
> Could you try snapshot 0.9-20100602113956+1000 and see if it fixes your
> problem?
>
>
>
> On 2/06/10 7:47 PM, Vaclav Pech wrote:
>
> The described architecture matches mine, however, 0.9-20100601084559+1000
> didn't help in my case.
>
> Vaclav
>
>
> On Wed, Jun 2, 2010 at 4:25 AM, Adam Murdoch <[email protected]> wrote:
>
>>
>>
>> On 1/06/10 8:58 PM, Vaclav Pech wrote:
>>
>> Hi Adam,
>>
>> thanks for looking into this. I'm on windows, jdk 1.6.0_18, using gradlew
>> 0.9-20100601084559+1000
>>
>>
>>  I think this problem happens when you run Gradle using the 64-bit jvm on
>> windows. I've created a fix and uploaded a new snapshot
>> 0.9-20100602113956+1000 to http://snapshots.dist.codehaus.org/gradle
>>
>> Could you give this a try and see if that fixes the problem?
>>
>>
>>
>> Vaclav
>>
>>
>>
>> On Tue, Jun 1, 2010 at 12:41 PM, Adam Murdoch <[email protected]> wrote:
>>
>>>
>>>
>>> On 1/06/10 8:23 PM, Vaclav Pech wrote:
>>>
>>> The problem might well be in GPars setup. Perhaps someone could give me
>>> helpful hints on how improper project setup can result in
>>> "java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils" thrown
>>> from gradle logging.
>>>
>>>
>>>  There shouldn't be any way that a project setup can cause this to
>>> happen. Possibly this is an environment problem. Which operating system and
>>> jvm are you using? And you're using the 0.9-20100601084559+1000 snapshot,
>>> not 0.9-preview-2?
>>>
>>> I will try the GPars build and see if I get the same problem.
>>>
>>>
>>>  We're not using apache commons in GPars at all.
>>> Could it be that in your setup apache commons happens to be on class path
>>> by accident?
>>>
>>> Vaclav
>>>
>>>
>>>
>>> On Tue, Jun 1, 2010 at 11:19 AM, Russel Winder <[email protected]>wrote:
>>>
>>>> On Tue, 2010-06-01 at 10:48 +0200, Vaclav Pech wrote:
>>>> > I confirm the fix of Bamboo build.
>>>> > However, local builds now fail with:
>>>> >
>>>>  I think this is not a Gradle problem.  The fact that the Bamboo build
>>>> works and it works for me locally using 1 test fork or 6 test forks on
>>>> my 8 core workstation, indicates that the issue you are seeing is likely
>>>> related to GPars and your context.   Sorry.
>>>>
>>>> --
>>>> Russel.
>>>>
>>>> =============================================================================
>>>> Dr Russel Winder      t: +44 20 7585 2200   voip:
>>>> sip:[email protected] <sip%[email protected]>
>>>> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
>>>> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>>>>
>>>
>>>
>>>
>>> --
>>> E-mail: [email protected]
>>> Blog: http://www.jroller.com/vaclav
>>> Linkedin page: http://www.linkedin.com/in/vaclavpech
>>>
>>>
>>>  --
>>> Adam Murdoch
>>> Gradle Developerhttp://www.gradle.org
>>> CTO, Gradle Inc. - Gradle Training, Support, Consultinghttp://www.gradle.biz
>>>
>>>
>>
>>
>> --
>> E-mail: [email protected]
>> Blog: http://www.jroller.com/vaclav
>> Linkedin page: http://www.linkedin.com/in/vaclavpech
>>
>>
>> --
>> Adam Murdoch
>> Gradle Developerhttp://www.gradle.org
>> CTO, Gradle Inc. - Gradle Training, Support, Consultinghttp://www.gradle.biz
>>
>>
>
>
> --
> E-mail: [email protected]
> Blog: http://www.jroller.com/vaclav
> Linkedin page: http://www.linkedin.com/in/vaclavpech
>
>
> --
> Adam Murdoch
> Gradle Developerhttp://www.gradle.org
> CTO, Gradle Inc. - Gradle Training, Support, Consultinghttp://www.gradle.biz
>
>


-- 
E-mail: [email protected]
Blog: http://www.jroller.com/vaclav
Linkedin page: http://www.linkedin.com/in/vaclavpech

Reply via email to