[GRADLE-2949] FinalizedBy vs DependsOn, difference in "gradle tasks" output Created: 06/Nov/13 Updated: 24/Jan/17 Resolved: 24/Jan/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Task | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Description |
Hi I have noticed that finlizedBy does not create the task dependency as dependsOn given example below: task taskX << { taskX.finalizedBy taskY "gradle tasks" would result in: Where changing it to dependsOn task taskX << { taskX.dependsOn taskY "gradle tasks" would result in: Is there any way to use dependsOn the way finalizedBy works. In other words I need finilizeBy to hide the tasks like dependsOn does and show dependencies when called gradle tasks --all Thanks Mike |
Comments |
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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 24/Jan/17 ] |
Since 3.3 the dependency report does not render any more task dependencies. Therefore, this issue is obsolete. |