I've migrate over to Gradle's new `plugins` system and for some reason the Android plugin needs me t...

# android

[krtko]

I've migrate over to Gradle's new plugins system and for some reason the Android plugin needs me to add

pluginManagement {
    repositories {
        gradlePluginPortal()
        jcenter()
        google()
    }
    resolutionStrategy {
        eachPlugin {
            if (requested.id.id.startsWith("com.android")) {
                useModule("com.android.tools.build:gradle:${requested.version}")
            }
        }
    }
}

to my settings.gradle file

[andrewreitz]

yeah it’s because they don’t publish to the gradle plugins portal, if you’re not using it on your top level gradle file you can still use the classpath way.

[gildor]

It explained in the official doc, and Android plugin mentioned as an example:
https://docs.gradle.org/current/userguide/kotlin_dsl.html#sec:plugins_resolution_strategy

[gildor]

it’s still looks very strange for me, that after all years and reported issues about it there is no solution

[andrewreitz]

oh yeah, it’d be nice if they published it correctly

[gildor]

They at least could publish plugin marker to their own google repo, it’s just a simple text file, so it would allow to get rid of resolutionStrategy, only custom repo would be required

pluginManagement {
    repositories {
        google()
    }
}

[itnoles]

You make it sounds like easy fix.

[gildor]

publish plugin marker is for sure easy, technically and I don’t see any legal problems

[gildor]

But publishing to Gradle Plugins Portal probably not so easy, not technically, but legally
Google doesn’t publish to maven/jcenter, only to own repo

[krtko]

Ya I get not publishing to a "non-google" repo but having to have the resolution strategy seems fixable.

[krtko]

Thanks for the answers btw