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

Gradle Community

short answer: yes. there's really no such thing as a lazy configuration right now.

But there is probably no problem with using `configureEach` either, it should currently just work the same. And when the configurations are changed to being used lazily eventually, it hopefully would just immediately work lazily.

fair enough, but _will_ they ever be lazy eventually? Is that even a meaningful concept for `Configuration`s?

Wouldn't it be meaningful for any container?
To not configure the contents if they are not needed.
Why configure the configurations if you are just calling `gradlew help --task compileJava` for example?

I always wondered what "configuring a configuration" would be :upside_down_face:

For example you will need to realize all configurations to find outgoing variants and resolvable configurations. So I don't see the necessity for lazy configurations