Eugene Krivobokov
03/25/2022, 8:19 AMdependencyResolutionManagement
are not used in some circumstances.
It happens only in included build in pluginManagement
https://github.com/gradle/gradle/issues/20259Vampire
03/25/2022, 9:00 AMdependencyResolutionManagement.repositories
is for production dependencies, not for plugins and their dependencies.
And besides that, pluginManagement { ... }
is evaluated separately from the remaining script first, as it could for example add a settings plugin using includeBuild
, that then can be applied outside the block.
Define your repository in pluginManagement.repositories
and it should probably work, as that is the place to define repositories for plugins and their dependencies.Eugene Krivobokov
03/25/2022, 9:27 AMpluginManagement.repositories
also has the same repositories:
pluginManagement {
repositories {
gradlePluginPortal()
mavenLocal()
mavenCentral()
}
}
Eugene Krivobokov
03/25/2022, 9:53 AMpluginManagement {
repositories { // FIX is here: they are used to build build-logic-settings
gradlePluginPortal()
mavenLocal()
mavenCentral()
}
includeBuild("build-logic-settings")
includeBuild("build-logic")
}
// plugins from build-logic-settings modifies pluginManagement in this project
plugins {
id("convention-plugins")
id("convention-dependencies")
id("convention-enterprise")
id("convention-cache")
}
Vampire
03/25/2022, 10:00 AMpluginManagement
block is executed separately from the remaining script as it can for example contribute settings plugins to be applied in the same script.Eugene Krivobokov
03/25/2022, 10:07 AM