This message was deleted.
# community-supports
Slackbot
05/19/2022, 6:52 PMThis message was deleted.
c
Clayton Walker
05/19/2022, 6:53 PMWe have a settings.gradle.kts and we have a plugin that does a tiny bit of setup
Copy code
plugins {
id("com.us.our-plugin") version "version"
}t
Thomas Broyer
05/19/2022, 7:02 PMUnfortunately no (AFAIK), at least not with
alias()buildSrc Copy code
plugins {
id("com.us.our-plugin")
}c
Clayton Walker
05/19/2022, 7:29 PMWasn't able to get alias working unfortunately, and also not able to get buildSrc working
Clayton Walker
05/19/2022, 7:30 PMIncluded build is working, but not from the classpath, I have to manually create a new plugin with the
Copy code
`java-gradle-plugin`Clayton Walker
05/19/2022, 7:32 PMSo yeah 2 bits of strangeness. api/implementation doesn't matter, the plugins aren't loaded. Also buildSrc strait up can't register a plugin that the settings.gradle file will load.
Clayton Walker
05/19/2022, 7:52 PMSo we were able to get it to work (super ugly) by moving from buildSrc to includeBuild, and from creating a new gradle plugin whose implementation was just the same as the plugin that we already had a dependency on.
v
Vampire
05/19/2022, 9:11 PMAlias will not work due to hen-and-egg.
Settings plugins should be able to bring in version catalogs, so you cannot use version catalogs before the settings plugins were applied.
And
buildSrcbuildSrcbuildSrcpluginManagementc
Clayton Walker
05/19/2022, 9:13 PMThanks @Vampire, this is new to me 'nowadays settings script is evaluated first'
Clayton Walker
05/19/2022, 9:14 PMDo you know why plugins included via dependencies in includeBuild aren't available to settings.gradle?
Clayton Walker
05/19/2022, 9:14 PMAnd I have to
Copy code
dependencies {
implementation(libs.our.settings.plugins)
}
gradlePlugin {
plugins {
register("settingsPluginHack") {
id = "our.settings-plugin"
implementationClass = "our.gradle.SettingsPlugin"
}
}
}Clayton Walker
05/19/2022, 9:15 PMWhere I have to re-declare a plugin with id
v
Vampire
05/19/2022, 9:15 PMIncluding a build does absolutely nothing as long as you don't need something from the included build.
In this case, if you don't use a settings plugin from that build, it (and its dependencies) are not added to the class path.
c
Clayton Walker
05/19/2022, 9:16 PMdon't need something from the included build.How do you specify a need? Other than the gradlePlugin block
Clayton Walker
05/19/2022, 9:16 PMOr is that/the convention plugins the only way?
v
Vampire
05/19/2022, 9:17 PMFor that case I think it is the only way.
For build scripts you could also use
buildscript { dependencies { ... } }c
Clayton Walker
05/19/2022, 9:17 PMhm
Clayton Walker
05/19/2022, 9:18 PMdoes that buildscript go into the includeBuild's build.gradle? Or in the root settings.gradle?
v
Vampire
05/19/2022, 9:18 PMInstead of redeclaring the plugin you could write a simple no-op pre-compiled script plugin, just to drag the dependencies to the class path
Vampire
05/19/2022, 9:18 PMI said "For build scripts you could also use"
✅ 1
Vampire
05/19/2022, 9:18 PMbuild script != settings script
Vampire
05/19/2022, 9:19 PMIf you want the classes of an included build available in a build script without applying a plugin from that included build
c
Clayton Walker
05/19/2022, 9:27 PMwhat do you mean by no-op pre-compiled script plugin?
v
Vampire
05/19/2022, 9:38 PMA precompiled script plugin that has no content and thus is no-op(eration).
You just apply it to drag in the transitive dependencies.
2 Views