[GRADLE-1825] importBuild creates redundant tasks for simple imported Targets Created: 11/Oct/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Blaine Simpson Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Let's say we have a top-level "importing" build file with Ant project name "importing", and an imported build file with Ant project name "imported". Say that both files define target "x". In both native Ant and through Gradle, these two targets/tasks are identified like "x" and "imported.x".

The problem is when an Ant target is imported but not overridden. Say we have target "y" defined only in the "nested" build file. In Ant this target is identified simply as "y". There is no ambiguity since there is no other task definition that it could be confused with, and the end-user has no need to know that it was defined in "imported" as opposed to in "importing". Gradle's "importBuild" messes this up and exposes two tasks for the one Ant target: "y" and "importing.y". The "importing.y" task is not only superfluous, but is misleading because it gives the appearance that the "y" target has been overridden. In Ant you can tell that a target has been overridden precisely because "ant -p" shows both the qualified name like "project.target" (for the nested target) and unqualified "target" (for the overriding target). In gradle there is no way for the end user to distinguish whether an imported target is overridden (in which case there are two targets to choose between) or not (in which case in Gradle there is a superfluous task and is doesn't matter which one is chosen).

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