Resolving all configurations is usually bad practice, because it might trigger work that could be avoided, which will make the build slower.
Comment From: wilkinsona
For tasks, using configureEach is recommended as it avoids eager creation of tasks that have been lazily registered. As far as I know, the same does not apply to configurations as there's no support for lazy registration. Furthermore, I don't think changing from all to configureEach has any bearing on whether or not the configuration is resolved and Gradle's own documentation uses configurations.all in places. Given this, I'm going to close this one as I don't think it will bring any noticeable benefit. Thanks anyway.