[GRADLE-1555] Programatic task depedencies not obeyed in tooling API Created: 16/May/11 Updated: 04/Jan/13 Resolved: 20/May/11
|Reporter:||Kris De Volder||Assignee:||Unassigned|
|Resolution:||Not A Bug||Votes:||0|
Reproducible from STS Gradle plugin.
Create a Gradle project with just a single build.gradle file in it and nothing else.
Do "Run As >> Gradle Build ..." on the build.gradle file.
Only :task1 was executed. Why not :task2 and :task3?
|Comment by Kris De Volder [ 16/May/11 ]|
Ok... so I just tried on the commandline and get the same result there.
So it isn't a problem with tooling API perse. Still it looks like the behavior is inconsistent with the docs. So I guess either the docs are wrong or this is a bug.
|Comment by Andrew Thorburn [ 17/May/11 ]|
Just a thought: You're making task0 depend on 2 & 3, not task1. Given that you are then trying to run task1, it's not all that surprising that 2 & 3 aren't executed - task1 doesn't depend on them, or any other tasks, as far as I can tell.
|Comment by Kris De Volder [ 17/May/11 ]|
Oops! I guess you can close this bug... "User Error"