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

Gradle Community

While you actually should not use it at all. :smile:
If you only define it as sole repository, nothing else will be used.

A bit more context:
I have a dependency that I am releasing to `mavenLocal`  repository for testing.  Since this is a test code I am always taking the "currently" released dependency using  dynamic dependency versions. Sometimes this may clash with `mavenCentral` repository resolution.
 (kind of ignore whatever is in in maven central) ?

BTW I would remove `mavenCentral` from my project, but I need other dependencies from there.

You can even do it on a per-dependency basis with "exclusiveContent" or how it was called

Ah, yeah, then the "exclusiveContent" thing is what you want

<https://docs.gradle.org/current/userguide/declaring_repositories.html#declaring_content_exclusively_found_in_one_repository>