I have replicated the project structure described in the user docs from here:
https://docs.gradle.org/current/userguide/multi_project_builds.html#ssub:dependencies_and_execution_order
…and the build fails with this error:
$ ./gradlew -q action
FAILURE: Build failed with an exception.
* What went wrong:
Task 'action' not found in root project 'messages'.
* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Is the documentation out of date? Does it depend on version 2.13? I’m running 2.12.
Whoops - sorry, I do have a significant difference.
The subprojects do not have build script files named build.gradle
, they are named test.gradle
instead. And, this is the contents of the settings.gradle
file:
rootProject.children.each { project -> project.buildFileName = "test.gradle" }
include 'consumer', 'producer'
I would like this organization to work, but with differently-named build script file names.
Ha! Duh.
Just realized my include statement was in the wrong place.
Never mind!