And by adding another dependency on 'compile' confgiruation I finally got
proper execution order:
dependencies {
...
compile project(':project-example-simple')
compile project(path: ':project-example-simple', configuration:
'sources')
}
So, only dependencies on 'compile' and probably other java configurations
are considered. However, I do not need project-distribution to be a 'java'
project. How could I make non-java project depend on the java one (on its
artifacts)?
My understanding of Gradle was that each project has number of
configurations and each configuration has input and output artifacts.
Project may depend on particular artifcat in particular configuration of
another project, and as Gradle knows which exact task produces the artifact,
it may organize proper execution order.
I don't see anything java-specific in this scheme, but it looks like my
understanding is wrong? Or is it a bug I've encountered (better to say a
BUG)?
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Gradle-does-not-honor-dependencies-in-multi-module-project-tp4329149p4329240.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
