[GRADLE-998] Detailed flow of gradle lifecycle Created: 22/Jun/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Jason Porter Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

A detailed overview of the gradle lifecycle would be very helpful for those of us doing more advanced things in builds and plugins. We need to know what's available to us at certain places in a build.gradle file and when things are evaluated. For example, what do I need to do to correctly find the source sets of subprojects? When does configuration end, and how can I tie into that, or get notified of when it's complete to add any further additional configuration. Steve and I have come across places where we need information that's contributed from plugins, but we don't know when / where the correct place is to hook into the lifecycle.

For the most part it's transparent to the users / build creators, but it would be very nice to have this transparency into the gradle process.

 Comments   
Comment by Hans Dockter [ 25/Jun/10 ]

I agree. That would be very important.

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 11:44:17 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.