[GRADLE-2336] Error during project evaluation hidden by an other error in afterEvaluate closure Created: 05/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Stephane Gallès Assignee: Unassigned
Resolution: Won't Fix Votes: 0


When evaluation of a project fails, the afterEvaluate closure is still called. If an other error is detected in this afterEvaluate, an other exception is thrown and hides the original cause of the error.

My use case :

  • an init script set an afterEvaluate closure. This closure is supposed to initialise an ext property that must be created by the main script.
  • the main script has a Groovy syntax error (and hence can not create the property )
    The afterEvaluate closure can not find the expected property an throws an other exception. The real cause of the problem (the syntax error) is hidden.

When the project can not be evaluated, should the afterEvaluate closure be still called ?

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