Hi folks. I'm pretty new to Gradle and am trying to improve the performance of a build. One thing I noticed in a build scan is that it is spending a non-trivial amount of time on network requests that are failing (see partial screenshot below). It is my understanding that these detachedConfigurations are generally coming from the spring boot dependency management plugin. Does anyone know if there's a way to instruct gradle to not even attempt to look for these files on an external maven repository?

Maybe repository content filtering? https://docs.gradle.org/current/userguide/declaring_repositories_adv.html#sec:repository-content-filtering

You mean ditching it in favor of the gradle platform bom support?

…and version catalogs, and dependency constraints, etc. https://docs.gradle.org/current/userguide/getting_started_dep_man.html

Switching over to using the spring boot bom directly solved the original issue. It did result in different dependency resolution which I'll have to read a bit more on. Thanks for the advice!

To say it even more clearly, the Spring Dependency Management plugin is a relict from times when Gradle did not have built-in BOM support, by now does more harm than good, and even its maintainer recommends not to use it anymore but instead the built-in BOM support. 🙂

Shameless plug: https://erichaag.dev/posts/bootiful-builds-best-practices-spring-boot-gradle/#7-replace-iospringdependency-management-with-a-gradle-platform