[GRADLE-2607] Lifecycle tasks not calling overwritten tasks Created: 21/Dec/12  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: 2


It looks like there is a bug in the lifecycle tasks in the Java plugin, specifically the "build" task. If I overwrite the "test" task from the Java plugin and execute "gradle test", Gradle correctly calls my overwritten version of the task. However, if I execute "gradle build" my overwritten version of the "test" task is not called.

Comment by Gradle Forums [ 21/Dec/12 ]

That's how it's currently designed to work, although it would sometimes be useful if dependencies were rebound to the overwriting task.

Comment by Gradle Forums [ 21/Dec/12 ]

This changed from 1.2 to 1.3 and blew our entire system out of the water. It should probably not work this way.

Comment by Gradle Forums [ 21/Dec/12 ]

That's surprising. I don't think I've ever seen it rebind dependencies.

Comment by Gradle Forums [ 21/Dec/12 ]

I've investigated this some more, and found the commit responsible for the changed behavior between 1.2 and 1.3. Bottom line is, it all depends on when the task dependency gets resolved, and it was never safe to rely on it being bound to the overwriting task. It would probably make a good feature, though.

As of today, the only way to make sure that task dependencies stay intact is to replace the task's actions, rather than the task itself. Of course this means that the task type can't be changed, but often that won't matter.

If you control the code that adds the task dependency, you can make sure that it gets resolved late by using a `String` (`foo.dependsOn("bar")`) rather than a `Task` (`foo.dependsOn(bar)`).

Comment by gilead [ 26/Mar/14 ]

A workaround: http://forums.gradle.org/gradle/topics/overriding_the_test_task_in_gradle_versions_1_1_doesnt_work_as_expected

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:26:31 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.