This message was deleted.

Laziness https://melix.github.io/blog/2022/05/gradle-laziness.html

Thought so, thanks. I kind of wish they would Mark which are which in the javadoc

agreed, the distinction across the Gradle API between eager/lazy is not at all clear. there was a rant somewhere on here a ways back with suggestions that Gradle should both clearly mark lazy/eager API methods, and deprecate / emit warnings when using eager methods.

emit warnings

would love if this was opt-in

I'd be just happy if it was on the javadoc

Unfortunately a warning on eager API is not so easy. Currently basically only the tasks container is designed to be lazy. There were cases already where the lazy API was used on a container and then the logic did not work because noone triggered the lazy handling anymore. So currently

all

and

configureEach

on built-in containers should not really make a difference except on the tasks container.

I would also say that I had a task that I had accidentally forgotten to make lazy... I made it lazy and our build time went from 5 minutes to 7. Thanks kotlin compiler...