This message was deleted.
# kotlin-dsls
Slackbot
12/15/2022, 10:17 PMThis message was deleted.
t
Taylor Smith
12/15/2022, 10:21 PMEssentially, we want to be able to expose something like
kotlin_version Copy code
kotlin("plugin.spring") version kotlin_versionv
Vampire
12/15/2022, 10:56 PMRegister an extension on the project that provides the value and that the consumer then can query.
Vampire
12/15/2022, 11:10 PMOr what I would recommend, make a version catalog that you share and can access from both projects in the case described in that SO post
t
Taylor Smith
12/16/2022, 12:13 AMHave a gap in my knowledge here related to extensions + kotlin.
Taylor Smith
12/16/2022, 12:14 AMFor my precompiled plugin project, I would apply the extension to root, correct?
Taylor Smith
12/16/2022, 12:23 AMso ideally I'd like to be able to apply this to root project and inherited in the other plugins downstream
Taylor Smith
12/16/2022, 12:24 AM Copy code
val kotlin_version: String by extra
dependencies {
implementation("org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:${kotlin_version}")
}Taylor Smith
12/16/2022, 12:24 AMthis pattern works for root, but not clear on how to also make this available when using the plugins
Taylor Smith
12/16/2022, 12:26 AMideally being able to just set the versions in
gradle.propertiesv
Vampire
12/16/2022, 12:38 AMI said extension, not extra property. Extra properties are practically always a dirty work-around instead of doing it properly.
Typically you would add the extension wherever you apply your convention plugin and there can use it.
But again, as this is about versions, dependencies, and plugins, I strongly recommend you have a look at version catalogs, where you also could use the same file in the main build and a build logic project to share the same values. You could even publish a version catalog and then user it similar to a dependency in multiple otherwise unrelated builds.
t
Taylor Smith
12/16/2022, 12:39 AMI see, researching
v
Vampire
12/16/2022, 12:41 AM2 Views