[GRADLE-1555] Programatic task depedencies not obeyed in tooling API Created: 16/May/11  Updated: 04/Jan/13  Resolved: 20/May/11

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
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.
In this build.gradle file paste the following code (from example 5.9 in the Gradle manual):

4.times { counter ->
    task "task$counter" << {
        println "I'm task number $counter"
task0.dependsOn task2, task3

Do "Run As >> Gradle Build ..." on the build.gradle file.


Note: the Gradle build daemon is an experimental feature.
As such, you may experience unexpected build failures. You may need to occasionally stop the daemon.
I'm task number 1


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"

Generated at Wed Jun 30 11:58:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.