[GRADLE-2769] 'projectsEvaluated' hook works differently in 'configure on demand' mode Created: 07/May/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

gradle.projectsEvaluated hook is fired after all projects are configured and before the task graph is build. Hence, users may use the hook to create task instances. In 'configure on demand' mode the projectsEvaluated hook is fired after the task graph is build. It's because the projects are actively configured on demand when the task graph is being built. Hence, if one uses projectsEvaluated to create task instances, it will not work in configure on demand mode. This behavior is 'silent', e.g. the task creation succeeds but it's not possible to run those tasks.

Fixing the behavior of this hook (or adding faster error feedback) is one of the things we plan doing to 'unincubate' configure-on-demand feature.

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