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

Gradle Community

image.png

Anyone got a clue why Gradle might start resolving project dependencies to published artifacts, instead of building them?

<https://scans.gradle.com/s/2h744qoyqz6oa/dependencies?dependencies=kotest-common&amp;expandAll&amp;focusedDependency=WzEwLDYsOTg2LFs5LDEsWzQwXV1d&amp;toggled=W1sxLDNdLFsxLDNdXQ>

left is local, right is on <https://github.com/kotest/kotest/actions/runs/9477409216/job/26111935515|GitHub CI>

Why is the dependency different???

The project is `:kotest:kotest-extensions:kotest-extensions-http`

I think it's something to do with the dependency here <https://github.com/kotest/kotest/blob/1f10a54bef99ea1e9ed4c6631dbe7dd7552cf165/kotest-extensions/kotest-extensions-http/build.gradle.kts#L26>

Fixed! There was a bug in the Kotest build config that set the project versions to an empty string, and Gradle reacted weirdly and the build scans didn't show any useful info.

<https://github.com/kotest/kotest/pull/4076#issuecomment-2162512191>