Gradle: Task declaring mustRunAfter is not taken under consideration with finalizer definition

[bmuschko]

This issue was originally report via GRADLE-3389. Given the following build script:

task A

task B {
    mustRunAfter "A"
    finalizedBy "C"
}

task C {
    dependsOn "A"
}

Expected Behavior

The task B should be run after `A. The expected output is the following:

:A UP-TO-DATE
:B UP-TO-DATE
:C UP-TO-DATE

Current Behavior

The actual output is the following:

:B UP-TO-DATE
:A UP-TO-DATE
:C UP-TO-DATE

Steps to Reproduce (for bugs)

See code example above.

[MrCeeJ]

Any update on this? It looks similar to a bug I am seeing..

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale[bot]]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.