Hello, I've got 3 subprojects which are connected by multi-project with
directory layout:

project-a/
              build.gradle
project-b/
              build.gradle

project-c/
              build.gradle

build.gradle
settings.gradle


In root build i want to add dependency task project-b:build to
project-a:build and project-c:build to project-b:build, so i'm expecting
execution order like c->b->a. In root build.gradle  i've got :

afterEvaluate{

project(':project-a').tasks.findByPath(':build').dependsOn(':project-b:build')

project(':project-b').tasks.findByPath(':build').dependsOn(':project-c:build')

 println  'dependencies for project a: ' +
project(':project-a').tasks.findByPath(':build').dependsOn
 println  'dependencies for project b: ' +
project(':project-b').tasks.findByPath(':build').dependsOn
 println  'dependencies for project c: ' +
project(':project-c').tasks.findByPath(':build').dependsOn

}


After running 'gradle build'   output:

dependencies for project a: [:project-c:build, :project-b:build]
dependencies for project b: [:project-c:build, :project-b:build]
dependencies for project c: [:project-c:build, :project-b:build]
:project-b:compileJava
:project-b:processResources
:project-b:classes
:project-b:jar
:project-b:assemble
:project-b:compileTestJava
:project-b:processTestResources
:project-b:testClasses
:project-b:test
:project-b:check
:project-b:build
:project-c:compileJava
:project-c:processResources
:project-c:classes
:project-c:jar
:project-c:assemble
:project-c:compileTestJava
:project-c:processTestResources
:project-c:testClasses
:project-c:test
:project-c:check
:project-c:build
:build
:project-a:compileJava
:project-a:processResources
:project-a:classes
:project-a:jar
:project-a:assemble
:project-a:compileTestJava
:project-a:processTestResources
:project-a:testClasses
:project-a:test
:project-a:check
:project-a:build

As you see  execution order is not what i expected: b->c->a
Question:
Why when i add task dependency precisely to project-a gradle is
automatically adding it to all subprojects? 
 
-- 
View this message in context: 
http://old.nabble.com/adding-task-dependency-through-%27dependsOn%27-on-subprojects-tp26817988p26817988.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


Reply via email to