[GRADLE-2514] afterEvaluate closure not executed when evaluationDependsOn is specified Created: 09/Oct/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Alex L Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Issue Links:
Related
Related to GRADLE-3231 Calling Project.afterEvaluate() on al... Resolved

 Description   

In a multi-project build, if there is an afterEvaluate closure defined for all subprojects, adding an evaluationDependsOn clause will cause the afterEvaluate closure to be skipped.

The correct behaviour would be for the afterEvaluate closure to be executed for all subprojects, no matter others subprojects' evaluation depend on them.

For example, supposing we have the following setup:

settings.gradle
include 'A', 'B', 'C', 'D'
build.gradle
subprojects {
	//println "Init: $project.name"
	
	if( project.name == 'A' ) {
		evaluationDependsOn( ':B' )
		evaluationDependsOn( ':D' )
	} else if( project.name == 'D' ) {
		evaluationDependsOn( ':C' )
	}
	
	afterEvaluate { subproject ->
		println "After eval: $subproject.name"
	}
	
}

task build;

Running gradle -q build should yeld 4 lines:

After eval: C
After eval: D
After eval: B
After eval: A

However, afterEvaluate is not executed for B and D, so it ends up with the following output:

After eval: C
After eval: A

I don't see why this would be the intended functionality, so I believe it is a flaw in the project evaluation procedure.

 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:

  • 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:24:01 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.