From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Re: the new `gradle.lifecycle.beforeProject {}` callbacks introduced in <https://docs.gradle.org/8.8/release-notes.html|8.8>, is there a reason they are on the `Gradle` class and not the `Settings` one? Calling them anywhere outside `settings.gradle[.kts]` fails with:
```GradleLifecycle#afterProject cannot be called after settings have been evaluated.```
Feels like this could be prevented at build time? Or is there a way to call them outside `Settings` ?

I've got code calling it from an init script

I wish new APIs would be less “stateful” and stop using a shared `Gradle` instance. Could the init scripts get another instance, `Init` maybe?