Hi Ed,

this is something we are working. You can rest assured that this should be
fixed soon. We might ask to try out one of our upcoming snapshots next week
that might already will solve your problem.

Hans



On Fri, Nov 4, 2011 at 11:55 AM, Ed Young <[email protected]> wrote:

> Did the Dependencies tab shed any light on the issue?
>
> I notice that I can't build offline, which makes me think that gradle is
> always looking to resolve the upstream repos. Is this correct?
>
>
> On Thu, Nov 3, 2011 at 7:49 PM, Ed Young <[email protected]> wrote:
>
>>
>>
>> Dependencies    Duration
>> All dependencies    50.814s
>> :testCompile    50.053s
>> :testRuntime    0.719s
>> :groovyCopy    0.041s
>> classpath    0.001s
>> :classpath    0s
>>
>>
>>
>>
>> On Thu, Nov 3, 2011 at 7:02 PM, Adam Murdoch <[email protected]
>> > wrote:
>>
>>>
>>> On 04/11/2011, at 11:29 AM, Ed Young wrote:
>>>
>>> Wow. 51 seconds for compileTestGroovy.
>>>
>>> Does that mean it's re-compiling all the groovy test files?
>>>
>>>
>>> It's almost certainly dependency resolution time. What time does it give
>>> on the 'dependency resolution' tab?
>>>
>>>
>>> This project has many many spec files and page spec files, but I'm not
>>> changing any of them and only executing 1 of them.
>>>
>>>
>>> Task    Duration    Result
>>> Project :    52.363s    (total)
>>> :compileTestGroovy    50.939s    UP-TO-DATE
>>> :test    1.402s    UP-TO-DATE
>>> :processTestResources    0.015s    UP-TO-DATE
>>> :classes    0.002s    UP-TO-DATE
>>> :compileJava    0.002s    UP-TO-DATE
>>> :compileGroovy    0.001s    UP-TO-DATE
>>> :compileTestJava    0.001s    UP-TO-DATE
>>> :processResources    0.001s    UP-TO-DATE
>>> :testClasses    0s    UP-TO-DATE
>>>
>>>
>>> On Thu, Nov 3, 2011 at 5:53 PM, Luke Daley <[email protected]>wrote:
>>>
>>>>
>>>> On 03/11/2011, at 11:50 PM, Ed Young wrote:
>>>>
>>>> actually, I'm not using any snapshots anymore, am I. I recently made
>>>> sure I was using only releases, but I hadn't removed the snapshot repos.
>>>> Good catch.
>>>>
>>>> repositories {
>>>>     mavenCentral()
>>>> //    maven { url "
>>>> http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/";
>>>> }
>>>> //    maven { url "
>>>> https://nexus.codehaus.org/content/repositories/snapshots"; }
>>>> //
>>>> //    mavenRepo url: [
>>>> //        "http://repository.codehaus.org";,
>>>> //        "http://snapshots.repository.codehaus.org";
>>>> //    ]
>>>> }
>>>>
>>>> This reduces my dev cycle to slightly less than 1 minute.
>>>>
>>>> Still not where I need to be. Any other ideas?
>>>>
>>>>
>>>> How long is the test task taking?
>>>>
>>>> You can run with --profile, which gives you a report
>>>> in <build_dir>/reports/profile.
>>>>
>>>> --
>>>> Luke Daley
>>>> Principal Engineer, Gradleware
>>>> http://gradleware.com
>>>>
>>>>
>>>
>>>
>>> --
>>> - Ed
>>>
>>>
>>>
>>> --
>>> Adam Murdoch
>>> Gradle Co-founder
>>> http://www.gradle.org
>>> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
>>> http://www.gradleware.com
>>>
>>>
>>
>>
>> --
>> - Ed
>>
>
>
>
> --
> - Ed
>

Reply via email to