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?
On Thu, Nov 3, 2011 at 5:33 PM, Luke Daley <[email protected]>wrote:
> The simplest way to make this faster would be to avoid the use of
> snapshots, is that possible?
>
> What snapshots are you using?
>
> On 03/11/2011, at 11:31 PM, Ed Young wrote:
>
> That had the effect of changing it from around 1 minute to more than 2
> minutes per dev cycle...
>
> I tried a couple variations on what you suggested:
>
> repositories {
> mavenCentral()
> maven { url "
> http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/"; }
> maven { url "https://nexus.codehaus.org/content/repositories/snapshots";
> }
> maven { url "http://repository.codehaus.org"; }
> maven { url "http://snapshots.repository.codehaus.org"; }
> }
>
> and
>
> 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";
> ]
> }
>
> I'm running gradle wrapper task 1.0-milestone-5, but I also tried by
> modifying my build to omit the wrapper task (commented it out) and it sped
> things up to 1 minute 30 or so.
>
> task wrapper(type: Wrapper) {
> //gradleVersion = '1.0-milestone-3'
> gradleVersion = '1.0-milestone-5'
> //distributionUrl = '
> http://repo.gradle.org/gradle/distributions-snapshots/gradle-1.0-milestone-5-20110927091445+0200-bin.zip
> '
> }
>
>
> On Thu, Nov 3, 2011 at 4:58 PM, Adam Murdoch
> <[email protected]>wrote:
>
>>
>> On 04/11/2011, at 9:33 AM, Ed Young wrote:
>>
>> certainly:
>>
>> repositories {
>> mavenCentral()
>> mavenRepo urls: [
>> "
>> http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/";,
>> "https://nexus.codehaus.org/content/repositories/snapshots";,
>> "http://repository.codehaus.org";,
>> "http://snapshots.repository.codehaus.org";
>> ]
>> }
>>
>>
>> Try this instead:
>>
>> repositories {
>> mavenCentral()
>> maven { url "
>> http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/"; }
>> maven { url "https://nexus.codehaus.org/content/repositories/snapshots";
>> }
>> ....
>> }
>>
>>
>>
>>
>>
>>
>> On Thu, Nov 3, 2011 at 3:42 PM, Adam Murdoch <[email protected]
>> > wrote:
>>
>>>
>>> Can you send in your repositories { } section, too?
>>>
>>> On 04/11/2011, at 6:38 AM, Ed Young wrote:
>>>
>>> This is a very simple geb test. It takes less then 10 seconds to run.
>>> The rest of the time it's sitting in:
>>> Building > :compileTestGroovy > Resolve dependencies ':testCompile'
>>>
>>> The project is modeled after
>>> https://github.com/geb/geb-example-gradle
>>>
>>> The dependencies :
>>>
>>> dependencies {
>>> //groovy "org.codehaus.groovy:groovy-all:1.7.5"
>>> groovy "org.codehaus.groovy:groovy-all:1.8.1"
>>>
>>> def gebVersion = "0.6.1"
>>> def seleniumVersion = "2.0rc3"
>>>
>>> // If using Spock, need to depend on geb-spock
>>> testCompile "org.codehaus.geb:geb-spock:$gebVersion"
>>> //testCompile "org.spockframework:spock-core:0.5-groovy-1.7"
>>> testCompile "org.spockframework:spock-core:0.5-groovy-1.8"
>>>
>>> // If using JUnit, need to depend on geb-junit (3 or 4)
>>> testCompile "org.codehaus.geb:geb-junit4:$gebVersion"
>>> testCompile "junit:junit-dep:4.8.2"
>>> testCompile "com.google.code.gson:gson:1.7.1"
>>>
>>> compile "org.codehaus.groovy.modules.http-builder:http-builder:0.5.1"
>>>
>>> // Drivers
>>> drivers.each { driver ->
>>> testCompile
>>> "org.seleniumhq.selenium:selenium-$driver-driver:$seleniumVersion"
>>> }
>>> }
>>>
>>> On Thu, Nov 3, 2011 at 1:16 PM, Robert Fischer <
>>> [email protected]> wrote:
>>>
>>>> What are you doing in your script body itself which is causing it to
>>>> take a minute to run?
>>>>
>>>> ~~ Robert.
>>>>
>>>>
>>>>
>>>> On Thu, Nov 3, 2011 at 3:06 PM, Ed Young <[email protected]> wrote:
>>>> > I need to speed up my development cycle, and I understand the with
>>>> > 1.0-milestone-5 the gradle daemon is greatly improved.
>>>> >
>>>> > How does one use the gradle daemon? I could use an example of how
>>>> it's used.
>>>> > The docs show command line options but no example.
>>>> >
>>>> > I usually build and run my geb tests like this:
>>>> > gradle test -Pt=SimpleNavSpec
>>>> >
>>>> > but that takes 1 min 10 seconds on a very fast laptop!
>>>> >
>>>> > CCHL-829706a:func-test-gradle-trunk eyoung2297k$ gradle test
>>>> > -Pt=SimpleNavSpec
>>>> > The 'urls' property of the RepositoryHandler.mavenRepo() method is
>>>> > deprecated and will be removed in a future version of Gradle. You
>>>> should use
>>>> > the 'url' property to define the core maven repository & the
>>>> 'artifactUrls'
>>>> > property to define any additional artifact locations.
>>>> > :compileJava UP-TO-DATE
>>>> > :compileGroovy UP-TO-DATE
>>>> > :processResources UP-TO-DATE
>>>> > :classes UP-TO-DATE
>>>> > :compileTestJava UP-TO-DATE
>>>> > :compileTestGroovy UP-TO-DATE
>>>> > :processTestResources UP-TO-DATE
>>>> > :testClasses UP-TO-DATE
>>>> > :test UP-TO-DATE
>>>> >
>>>> > BUILD SUCCESSFUL
>>>> >
>>>> > Total time: 1 mins 9.609 secs
>>>> >
>>>> > How can I speed this up using the gradle daemon?
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>> http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> - Ed
>>>
>>>
>>>
>>> --
>>> Adam Murdoch
>>> Gradle Co-founder
>>> http://www.gradle.org
>>> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
>>> http://www.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
>
>
> --
> Luke Daley
> Principal Engineer, Gradleware
> http://gradleware.com
>
>
--
- Ed
