It is possible to solve the problem partly, by adding dependency to
java-specific 'compile' configuration:
dependencies {
...
compile project(':project-example-simple')
}
then build output is:
:project-example-simple:compileJava
:project-example-simple:processResources UP-TO-DATE
:project-example-simple:classes
:project-example-simple:jar
:project-distribution:compileJava UP-TO-DATE
:project-distribution:processResources UP-TO-DATE
:project-distribution:classes UP-TO-DATE
:project-distribution:jar
:project-distribution:prepareDistribution
:project-distribution:buildDistribution
:project-distribution:sourcesJar
:project-distribution:assemble
:project-distribution:check
:project-distribution:build
:project-example-simple:sourcesJar
:project-example-simple:assemble
:project-example-simple:check
:project-example-simple:build
Still distribution project does not get sourcesJar (which is assigned to the
custom 'sources' configuration in project-example-simple). Looks like only
dependencies on java-specific configurations are taken into account by
Gradle when it arranges tasks. Is that correct?
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Gradle-does-not-honor-dependencies-in-multi-module-project-tp4329149p4329208.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
