[GRADLE-3268] Clarify user guide regarding running of finalizer tasks when finalized task is not run Created: 24/Mar/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


According to [1]the Gradle docs,

finalizer tasks are not executed if the finalized task didn't do any work, for example if it is considered up to date

However, as per [2]this question on StackOverflow, the following test case does not conform to the documented behavior:

task taskY << {

println 'taskY'


task taskX {


{ true }

finalizedBy taskY


{ println 'taskX' }


When gradle taskX or ./gradlew taskX are run (at least for Gradle 2.3), the following output is produced, clearly indicating that taskX is skipped due to being up-to-date, yet taskY still runs.



[1] http://www.gradle.org/docs/current/userguide/more_about_tasks.html#N11018
[2] http://stackoverflow.com/questions/29178153/why-is-this-finalizer-running-even-when-the-finalized-task-is-up-to-date

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:44:22 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.