[GRADLE-2071] Different task execution order Created: 27/Jan/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: 0


 Description   

I have simple multiproject build with one parent and one child (called subproject).

If I configure the child project in parent's build.gradle:

dependsOnChildren()
apply plugin: 'java'

project(':subproject') {
apply plugin: 'java'
}

the tasks are exucuted in this order:

$ gradle classes
:sub:compileJava UP-TO-DATE
:compileJava UP-TO-DATE
:sub:processResources UP-TO-DATE
:processResources UP-TO-DATE
:sub:classes UP-TO-DATE
:classes UP-TO-DATE
BUILD SUCCESSFUL

But when I configure it in subproject/build.gradle

    1. build.gradle
      dependsOnChildren()
      apply plugin: 'java'
    1. subproject/build.gradle
      apply plugin: 'java'

the tasks are executed in different order:

$ gradle classes
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:sub:compileJava UP-TO-DATE
:sub:processResources UP-TO-DATE
:sub:classes UP-TO-DATE
BUILD SUCCESSFUL

Why is the task exucution order different? I've read throught all the documentation, but haven't found an answer for this behaviour.
I checked it with gradle 1.0-milestone-3, 6 and 7

Thanks a lot,
Pavel

 Comments   
Comment by Gradle Forums [ 27/Jan/12 ]

dependsOnChildren() is executed against the current project. So, if you configure that in your subproject you're making the subproject depending on its children. It's different than configuring the root project to depend on its children.

dependsOnChildren() is the same as: project.dependsOnChildren() The project is different depending where the configuration lives (e.g. which build.gradle, etc.)

Hope that helps!

Comment by Gradle Forums [ 27/Jan/12 ]

Hi, thanks for quick answer.
Maybe you overlooked it, but in code samples I sent, the dependsOnChildren() is always in parent project - even in the second sample (there are comments with filename).

Comment by Gradle Forums [ 27/Jan/12 ]

I think it's a bug. A workaround is to put this at the very end of the parent build script, replacing an earlier `dependsOnChildren()`:

dependsOnChildren(true)

Comment by Gradle Forums [ 27/Jan/12 ]

dependsOnChildren(true) works fine.
Thanks.

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