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

This is by-design: repositories are never inherited. The project using a dependency (be it external or from an included build) has to declare the needed repositories. This applies to both project dependencies (and their transitives), and plugins and their dependencies.

Funny thing though, is that the repositories are inherited for every single other project. And it works just fine (for plugins and project dependencies). Only difference is they are not included by a plugin. The issue is that the project dependencies are using the plugin repositories for some weird reason.

In fact, that's the whole point of the `dependencyResolutionManagement` block.
<https://docs.gradle.org/current/userguide/dependency_management.html>
"Repositories used by convention by every subproject can be declared in the `settings.gradle(.kts)` file:"

"The `dependencyResolutionManagement` repositories block accepts the same notations as in a project, which includes Maven or Ivy repositories, with or without credentials, etc.
By default, repositories declared by a project will *override* whatever is declared in settings. You can change this behavior to make sure that you always use the settings repositories:"

You can then extend this and apply the `dependencyResolutionManagement` block to every build by applying the same settings plugin to each build.

So, I guess I must be misunderstanding what you're saying.

Tbh, it was much text and there can easily be things misunderstood. Can you maybe knit an <https://stackoverflow.com/help/mcve|MCVE> that demonstrate your situation? Would probably clear up things.

But generally, if you say the standard plugin portal repository is used to resolve something, then you are talking about a plugin or is dependencies. That there `dependencyResolutionManagement` is not used is expected, because that is for normal dependencies. For plugins, `pluginManagement` is the relevant part.

Yeah, I thought I might need to do that. I'll go ahead and do that later and make a post with a minimum example showcasing the issue.

I ended up fixing my issue by adding the repository that contained that jar that was being looked up in the plugins repository to the common `pluginManagement` block in my settings plugin and everything seems to work. Doesn't make sense why only that repository is needed and not everything else, but I suppose it's working for the time being.