Hans Dockter wrote:
In Gradle trunk there is a bug regarding the handling of settings.gradle.
The following rule is no longer obeyed: If a settings.gradle file is
found, Gradle checks if the current project is part of the
multiproject hierarchy defined in the found settings.gradle file. If
not, the build is executed as a single project build. Otherwise a
multiproject build is executed.
Isn't this exactly what's happening?
When you run gradle down in the samples dir:
- it searches up
- finds the settings.gradle in the root dir of the source tree
- attempts to evaluates the buildSrc project
- fails because buildSrc/build.gradle is written against an older
version of gradle
If you run gradlew, rather than gradle, down in the samples dir, it all
works fine:
- it searches up
- finds the settings.gradle in the root dir of the source tree
- evaluates the buildSrc project
- evaluates the settings.gradle script
- decides that there's no project whose project dir == current dir
- executes a single-project build using build.gradle in the current dir
The problem is that we only just recently added a settings.gradle to the
root dir of the source tree, and that buildSrc project requires an older
snapshot of Gradle.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
