[GRADLE-2488] Sub-projects don't take on their parents' default tasks when Gradle runs from subdir? Created: 19/Sep/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

I'm not sure I understand default task inheritance. The Gradle docs [1]say: "In a multi-project build every subproject can have its own specific default tasks. If a subproject does not specify default tasks, the default tasks of the parent project are used (if defined)."

I tested this with the following code. A root project ("projectA"):

defaultTasks 'a'

task a {}

A child project (":projectA:childProject") :

task a {}

And a settings.gradle file:

include "childProject"

If I run "gradle" from the root project, both "a" tasks get executed. If I run "gradle" from the child project, however, no tasks are executed:

C:\projectA\childProject>gradle
root: a
child: a
:childProject:help

Why does the sub-project only take on the root default tasks if executed from the root?
----------------------------------------------------------------------------------------
[1] http://gradle.org/docs/current/userguide/tutorial_using_tasks.html#sec:default_tasks

 Comments   
Comment by Gradle Forums [ 19/Sep/12 ]

Is this expected / default behavior?

Comment by Gradle Forums [ 19/Sep/12 ]

Sounds like a bug to me. You should be able to work around with something like `allprojects

{ defaultTasks 'a' }

`.

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