is there a way to have a settings plugin add a plu...
# plugin-developmentj
John
05/16/2024, 9:34 PMis there a way to have a settings plugin add a plugin to the classpath so that the plugin can be applied via id (no version) in the root build.gradle? right now I am adding the dependencies via
gradle.rootProject.buildscript.dependenciesorg.gradle.api.plugins.UnknownPluginException: Plugin [id: '...'] was not found in any of the following sources:John
05/16/2024, 9:39 PMin my project that uses the settings plugin, if i put
Copy code
buildscript {
dependencies {
classpath("myplugin")
}
}John
05/16/2024, 9:39 PMbut i can't seem to replicate that in the settings plugin
v
Vampire
05/17/2024, 6:53 AMJust depend on that other plugin, that's it.
j
John
05/17/2024, 1:28 PMyeah, i was hoping to choose the version based on logic within the settings project though, but this will be my fallback plan
John
05/17/2024, 1:28 PMi was surprised gradle.rootProject didnt work for the.... root project
v
Vampire
05/17/2024, 1:53 PMThe buildscript dependencies in the settings script works, as it is like depending on it, you add it to the classloader for the settings script which is a parent class loader of the build script
Vampire
05/17/2024, 1:53 PMBut if you add it to the buildscript classpath of the build script manually it will also not be found for usage in the plugins block by id
Vampire
05/17/2024, 1:54 PMThe plugins block is extracted and evaluated separately in a dummy project to find out which type-safe accessors to generate.
Vampire
05/17/2024, 1:54 PMAnd there the addition of the buildscript classpath of the build script would not be available either
j
John
05/20/2024, 1:53 AMYeah. I was previously using a custom wrapper to declare pluginManagement so that plugins can be declared in projects by id with no version. But since pluginManagement doesn't actually add it to the class path (the actual plugins{} usage is what triggers this.) Then we would still have issues where plugins applied only at subproject level would get the wrong versions of dependencies (if that transitive dep was already resolved at root level). So my new idea is to use a settings plugin to manage the root buildscript directly. But for some reason plugins added this way via rootProject.buildscript are not available to apply via ID in the root project, only subprojects
John
05/20/2024, 1:58 AMI.know i could do that with the wrapper too, but i have some other reasons why I want the extra layer of wrapper -> settings plugin -> project plugins too
24 Views