I’ve been developing my plugin for some time now and while testing it I’ve encountered funny issue. My project uses some dependencies which aren’t available on mavenCentral and therefore use 3rd party repositories. Whenever I attempt to apply my plugin to a testing project, gradle build fails sayin…

That’s exactly the idiomatic way. A project that applies a plugin is responsible to define all repositories that are necessary to resolve the plugin and all its transitive dependencies. Think for example about a corporate environment where there is a rule to only use in-house repository mirrors, w…

Hmm I see what you mean, but isn’t there a way to declare the missing repositoriers for the project directly in the plugin? something like you have project.afterEvaluate, and you could just specify the repositories there, without making the consumer touch anything else than actually applying the plu…

Actually I was thinking of adding this block of code before any code evaluation, but that doesn’t seem to work either: target.gradle.settingsEvaluated { settings -> settings.pluginManagement { spec -> spec.repositories { repo -> repo.maven { …

but isn’t there a way to declare the missing repositoriers for the project directly in the plugin? No something like you have project.afterEvaluate afterEvaluate anyway is almost always an error. It usually only does symptom treatment, shifting the actual problem to a later, harder to reprodu…

Alright this makes sense for me, so ideal setup for this would be to have some sort of bootstrap plugin which would apply the real plugin as well with all the dependencies?

No, as I said, I would make the real plugin and additionally a settings plugin that only declares those repositories and then let the consumer decide where the real plugin needs to be applied and whether he wants to apply the settings plugin or not.

Thanks for the tip, I started working on it and found out that I can’t specify version of the plugin when I want to apply it in my settings plugin using project.plugins.apply(name). How should I be applying it?

I said you should not :slight_smile:

How to properly distribute my plugin in my case?

Help/Discuss

Vampire (Björn Kautler) October 18, 2023, 12:41pm 9

I said you should not

Topic		Replies	Views
Adding a plugin with dependencies of a specific maven repository Plugin Portal not-a-bug	8	4421	December 13, 2018
Dependency resolution in plugin depending on the package from custom repository Help/Discuss	6	1002	September 18, 2018
Gradle isn't serching the right repository for plugins Help/Discuss	2	4407	September 27, 2022
Confusion over plugin dependencies Help/Discuss	9	1699	January 27, 2017
Can Plugins DSL work with a repo other than the gradle plugins portal Help/Discuss	1	315	January 7, 2020

How to properly distribute my plugin in my case?

Related topics