If I have a Kotlin gradle script file that I want to apply to a project

./gradle/deps.gradle.kts

, do I have a way of statically accessing the file’s classes it defines externally in another kotlin file where I do something like this:

plugins {
  `kotlin-dsl`
}

buildscript {
  apply {
    file(File(project.rootDir, "gradle/deps.gradle.kts"))
  }

  dependencies {
    classpath(Plugins.kotlin) // Unresolved reference error
  }
}

I don't think so, generally the recommendation is to use

buildSrc

for that

I had all my dependencies setup in a file inside my

buildSrc

, but now I’m trying to add some extension methods for the

multiplatform

plugin inside of

buildSrc

. The file I posted above is actually the

./buildSrc/build.gradle.kts

file. It’s important for circleci caching reasons that I have all my dependency information inside a single file, and I’m trying not to duplicate my kotlin version into 2 locations.

curious as to why you're adding the kotlin plugin to the classpath there then

I want to be able to access the

multiplatform

plugin classes, so that I can add some extension methods for the plugin to my

buildSrc

right, but that means it's a regular dependency of the buildSrc project, i.e. use the normal

dependencies {}

block

oh - good call

yes, but if you can manage to parse the file instead, then at least that works somewhat

my plan was to move my dependencies file to a file that could be applied

if you add the dependencies in

deps.gradle.kts

instead, it might work

whats what I’m trying

right, you can't get the classes from inside

I’m not 100% sure - but am I required to define things on the

ext

, to gain access outside of there

then you don't need the class

oh - I can’t do that. My team has like 50 modules

yea, probably

I guess my best option is to duplicate the logic, and just explicitly declare the dependency here?

yea

😞 Oh well

might be a good idea to file an issue with gradle for this sort of use-case

thanks for your help!

it's usually only an issue with the kotlin plugin, but it is a pretty bad pain point

I’ll do that

Kotlin is statically typed language, it will not work with dynamically applied script, because there is no way to resolve members of dynamically applied script on compilation time