Callback after plugin initialisation done and plugin extension configured?

[Lance (uklance)]

Take a look at this thread which discusses some lazy configuration techniques that can help you avoid afterEvaluate including

• the “live” collection methods on DomainObjectCollection (eg all(Closure) or matching(Closure))
• Property and Provider (see lazy-configuration )

Unit test plugin's afterEvaulate

Lately I started writing my first gradle plugin (gradle 6.4.1) and used gradle init with selection 421 (Gradle Plugin, Java, Groovy) as starting point. My plugin features an extension (similar to the Java plugin’s sourceSets) with a NamedDomainObjectContainer in it. For each container entry a task will be created like apply${containerName}. Task creation is done the in the project’s afterEvaluate callback: aProject.afterEvaluate((p) -> { final MyExtension myExtension = p.getExtensions().getB…