@madorb The basic groovy based assumptions that variables would be accessible via magic isn't true with GSK. Anything that you thought you could just access from thin air you now need to figure out where it originates from and ask that object for it. For example, you need to ask the

project.properties

for properties.

Its one of the confusing things that takes most first time GSK users a bit of time to get used to (at least this was true for me)

thanks @Czar @jlleitschuh that's helpful. i know dev is still ongoing, at some point i assume there will be some documentation about mapping patterns from Groovy -> Kotlin

i decided to hold off on the journey of moving to GSK and focus on kotlinifying the java code of my app for the time being as I just couldn't quite enough detail out of the existing documentation to determine how to map all my patterns

Thats fair. It's not intuitive at first but neither was gradle to me. Once I worked in it for a while it started to make sense.

I ended up using the build file that is used to build GSK as my primary example.

Gradle/kotlin-dsl starts from 14124

I bumped Gradle from 3.5. to 4.0 Now, my

:compileTestKotlin

started failing, because it doesn't see classes compiled by

:compileKotlin

Did you encounter the same issue?

I found a workaround:

val mainCompilation = tasks["compileKotlin"] as KotlinCompile
val testCompilation = tasks["compileTestKotlin"] as KotlinCompile
testCompilation.classpath = testCompilation.classpath.plus(files(mainCompilation.destinationDir))

Also, after the bump to Gradle 4.0,

:test

stopped working:

Skipping task ':test' as it has no source files and no previous output files.

I'm trying various fixes.

https://docs.gradle.org/4.0/release-notes.html#location-of-classes-in-the-build-directory :

Plugins, tasks or builds that used hardcoded paths may fail.

@bamboo there used to be a feature to get the kotlin dependencies version automatically from the applied

kotlin("jvm")

plugin. Seems it’s not working any more

plugins {
 kotlin("jvm", "1.1.3")
}

dependencies {
    compile(kotlin("stdlib-jre8"))
    compile("io.airlift:airline:0.7")
}

runtime - Runtime dependencies for source set 'main' (deprecated, use 'runtimeOnly ' instead).
+--- org.jetbrains.kotlin:kotlin-stdlib-jre8:1.1.2-5
|    \--- org.jetbrains.kotlin:kotlin-stdlib-jre7:1.1.2-5
|         \--- org.jetbrains.kotlin:kotlin-stdlib:1.1.2-5
|              \--- org.jetbrains:annotations:13.0
+--- io.airlift:airline:0.7
|    +--- javax.inject:javax.inject:1
|    +--- com.google.code.findbugs:annotations:2.0.3
|    \--- com.google.guava:guava:18.0
+--- org.jetbrains.kotlin:kotlin-stdlib:1.1.2-5 (*)
\--- org.jetbrains.kotlin:kotlin-reflect:1.1.2-5

For a pure Kotlin codebase, the workaround with the currently best results is:

tasks["compileKotlin"].outputs.dir(File(buildDir, "classes/main"))
tasks["compileTestKotlin"].outputs.dir(File(buildDir, "classes/test"))

It seems that the Kotlin Gradle plugin might need an update 1 reply For a pure Kotlin codebase, the workaround with the currently best results is:

tasks["compileKotlin"].outputs.dir(File(buildDir, "classes/main"))
tasks["compileTestKotlin"].outputs.dir(File(buildDir, "classes/test"))

Gradle Summit 2017 talk by @bamboo about gradle/kotlin-dsl K

And one more from Rodrigo and @nadavc

Rodrigo and Nadav thanks for these really nice talks and your work 👍

Thanks, Andrey 👍

Is there a proper procedure that needs to be followed when changing the Gradle wrapper (from v3.3 to v4.0) in IntelliJ? Last time I attempted to do it IntelliJ would not properly recognise a written build.gradle.kts file the first time round. 🙁. Would be great to change the Gradle wrapper without having to reopen the project in order to get things working.

@napperley Probably

./gradlew wrapper --gradle-version=4.0 --distribution-type=all

I see everywhere something like

plugins {
    base
...
}

But the documentation link says there is no such thing. (https://docs.gradle.org/current/userguide/base_plugin.html) what is the base plugin and why is it in kotlin samples?

I get this “IDE Fatal Error” and it points to the “<caret>” position in the code.

Where are program arguments set with Kotlin DSL?

In Kotlin DSL is there a way to customise the run task (eg add program arguments)?

@napperley check out this video, I think it covers what your looking for:

they add custom arguments to a run task at around 15100

@napperley If you use application plugin and “run” task:

tasks {
    "run"(JavaExec::class) {
        args = listOf("a", "b", "c")
    }
}
//or
val run: JavaExec by tasks
run.args = listOf("a", "b", "c")

hello! i'm trying to build `hello-android' from official kotlin-dsl repo. i've got this: all is red and doesn't compile.

Error:Internal error: unable to compile script, see log for details

does anybody expect same issue on AS 3.0 p4?

@bamboo Similar wacky reflection magic as that other plugin used but this time using the gradle API to do it instead of groovy meta-class monkey patching: https://github.com/junit-team/junit5/blob/6ded3d033b33d313767550dbd7fc0611f6a485b4/junit-platform-gradle-plugin/src/main/groovy/org/junit/platform/gradle/plugin/JUnitPlatformPlugin.groovy#L30-L35 Thankfully your code snippet you gave me a few months ago worked as a workaround.