Adding module(Object notation) to PluginDependenciesSpec

Would the gradle devs be willing to add something like a module(Object notation) method to PluginDependenciesSpec that would allow users to use a dependency notation to easily apply a plugin that isn’t in the plugin repository.

This would be useful for plugins that are included builds of a composite build.

This would obviate boilerplate in settings.gradle.kts like the following:

pluginManagement {
    resolutionStrategy {
        eachPlugin {
            if ( == "my-plugin") {
                useModule(mapOf("group" to "my-group", "name" to "my-artifact", "version" to requested.version))

Composite builds should (and will eventually) just work, no module notation necessary :slight_smile:

1 Like


Is there any ETA for this? Is it anticipated for 4.9, 4.10, …, 5.0, etc.?

Is there a GitHub issue for this? If not, do you want me to make one?

Is there any public roadmap for future Gradle releases?

Thanks for working on this.

See I can’t give you a timeline yet. I hope the workaround does the trick for you in the meantime.

1 Like