Hey guys. I’m trying to migrate my project from Gradle to kotlin-dsl. One issue I’m struggling with is the usage of Gradle’s

apply from:

directive. Simplifying, when my

build.gradle.kts

file looks like this:

plugins {
   id("kotlin-android-extensions")
}

androidExtensions {
  isExperimental = true
}

it’s works fine. However, when I try to extract plugin definition to a separated file and apply it from my `build.gradle.kts`:

apply{
  from("$rootDir/kotlin_shared.gradle.kts") //contains plugins { id("kotlin-android-extensions") }
}

androidExtensions {
  isExperimental = true
}

it fails on

"Unresolved reference: androidExtensions"

. In Groovy version I had

apply from:

directive on top of my

build.gradle

file and it worked pretty well. Seems like kotlin’s

apply { from () }

doesn’t work like Gradle’s

apply from:

version, or am I missing sth?

The second block of code you're showing no longer uses the

plugins

block, and you should use it for it to work better

yup, the top level accessors (

androidExtensions

in this case) are only generated when they are applied in the

plugins {}

block gradle does like a 2 phase compilation, and since the

apply(from = "...")

is executed and not handled in the same way, gradle doesnt know about it so you either use

plugins {}

block to get accessors or need to know the type and do something like

configure<org.android.AndroidExtension> {}

you can use the

./gradlew kotlinDslAccessorsReport

to see what is generated by the

kotlin-dal

fine, I get it. Then why something like this doesn’t work either: https://github.com/mgrzechocinski/kstarter/pull/5/files

static accessors for script plugins are not yet implemented: https://github.com/gradle/kotlin-dsl/issues/427 / https://github.com/gradle/kotlin-dsl/issues/432

I’m just wondering what’s the best way of sharing some common configuration code between different gradle modules. Currently, I have around 20 of them and they all need to access certain piece of shared configuration

yeah i hear ya the most common way ive seen it is using

buildSrc

for example, https://github.com/gradle/kotlin-dsl/blob/master/buildSrc/build.gradle.kts#L21 and using https://github.com/gradle/kotlin-dsl/tree/master/buildSrc/src/main/kotlin/plugins then the plugin ids can be consumed from the main build in a multi-project build

yup, I already use

buildSrc

for my dependencies catalog which I refer to from different modules

Use buildSrc for that, you can share any piece of config there as plugin or extension function

cool, thanks!

@gildor I am having problem with this too

What kind problem?

when I try to apply from a file

not sure that it’s related to this thread.

yep, I think it is the same problem really, when you use apply from + buildSrc

Most probably you have this problem because you use allprojects/subprojects block on a project that doesn’t apply plugin with this configuration (java/kotlin/android)

I am gonna try

so or you have to apply plugin (it’s possible in buildSrc only with precompiled script plugins) or just use dynamic syntax:

"implementation"(Dependencies.kotlin)

if I change implementation for "implementation" the old error dissapear but I got

Configuration with name 'implementation' not found.

so, plugin where you apply this dependency doesn’t have implementation configuraion

so I need to add the plugin there?

see,

implementation

is a configuration that provided by java plugin (also implicitly used by java), check that this project where you apply this dependency have it

I am trying to port build.gradle files to kts

yes, I understand, but where do you see this error, how buildSrc related to apply (because usually no reason to use apply with any buildSrc code)

maybe it is not a problem of buildSrc

this plugin applies com.android.application plugin, so it sould work (and probably works in this project)

I am gonna try to convert directly this project

Yes, because you need static accessors or use dynamic plugin application syntax

really I got it working when I don't try to use from another files

Yes, that what I'm saying apply scripts is dynamic feature, you cannot use almost anything in script plugin, official guide explains this and provide solutions

Check this project