StackOverflow during simple file copy in Gradle 1.8

(Matt Khan) #1

I have a task includes the following action

project.copy {
CopySpec cs ->
 cs.includeEmptyDirs = false

and which now produces a stackoverflow in this code

at org.gradle.api.internal.file.CompositeFileCollection$1.resolve(
        at org.gradle.api.internal.file.CompositeFileTree$FilteredFileTree.resolve(
        at org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.resolveNested(
        at org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.doResolve(
        at org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.resolveAsFileTrees(
        at org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext$FileTreeConverter.convertInto(
        at org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.doResolve(

This worked in gradle 1.0-1.6

Any idea what is going wrong or how to debug this?

(Peter Niederwieser) #2

I’m not able to reproduce this. Can you post a minimal self-contained example that allows to reproduce the issue?

(Matt Khan) #3

It looks like it is related to use of GString, put the following in a build.gradle and run it using gradle 1.8

task doIt {
    ext {
        source = "a"
        dest = "b"
    doLast {
        project.copy { CopySpec cs ->

result = stackoverflow

If you pass source.toString() and dest.toString() instead and it works fine.

If you use gradle 1.7 instead (and pass the gstring referencess in), it also works fine hence is clearly a regression in 1.8 If you don’t use a reference and pass “a” in directly, it also works fine.

(Peter Niederwieser) #4

‘“a”’ and ‘“b”’ aren’t GStrings (they don’t contain a ‘$’).

(Peter Niederwieser) #5

As of 1.8, ‘source’ inside ‘project.copy’ gets resolved to ‘CopySpec.getSource()’. In earlier versions, it gets resolved to ‘doIt.ext.source’. Not sure which is right, but it needs to be investigated. Raised GRADLE-2902. Meanwhile, renaming ‘doIt.ext.source’ will solve the problem.

(Matt Khan) #6

Ah OK, I simplified my example too far (my actual case contains $)

(Matt Khan) #7

OK thanks. Quick fixes are good!