I'm thing I'd like to understand conceptually is how the classpath works. With groovy syntax when I add a plugin like

com.google.protobuf

I now have available

protobuf

as a keyword. Is there an equivalent process that happens with adding plugins to a Kotlin build script? And how does Kotlin script handle classpath / imports when only one project within a larger build adds a plugin, especially given that Kotlin script seems to require imports at the top level?

Hi all! I'm trying to figure how to share functions in multi-project builds. With groovy based gradle scripts, this is as simple as that: Parent build.gradle:

void hello() {
        println "Hello World!"
}

Child build.gradle:

// Will print Hello World when gradle is invoked
hello()

This no longer works for kotlin based build scripts, the method reference is just considered as undefined. Any idea how can I best fill this gap? Should I raise an issue for such use case?

The Google App Engine Gradle Plugin creates an extension, AppEngineExtension, which then registers a "tools" extension. In groovy script this can be used like this: appengine { tools { cloudSdkHome = "blah" } } But in Kotlin script I cannot see how to do the same. Does anyone know how this can be configured?

i start a thread

Right, but since those expressions are modifying the root project's buildscript, one can't replicate a groovy-based multi-project build in which subprojects have their own buildscript

Does anyone know how I configure

dependencyManagement

with gradle-kotlin-script ?

Hello everyone! Is there any way I can merge these two ways of declaring/including plug-ins in Gradle?

plugins {
  application
  id("org.jetbrains.kotlin.jvm") version "1.1.2-2"
  //id("org.jetbrains.kotlin.plugin.spring") version "1.1.2-2"
}

apply {
  plugin("io.spring.dependency-management")
  plugin("kotlin")
  //plugin("kotlin-jpa")
  //plugin("kotlin-spring")
  plugin("org.springframework.boot")
}

I'm also interested how I'd do something like add a dynamic configuration / source set with `kotlin-script-gradle`:

configurations {
    provided
}
 
sourceSets {
    main {
        compileClasspath += configurations.provided
        runtimeClasspath += configurations.provided
    }
    test {
        compileClasspath += configurations.provided
        runtimeClasspath += configurations.provided
    }
    customSourceSet
}
 
dependencies {
    provided project(':Core')
}

I'm assuming I'd need to think of it differently with

gradle-kotlin-script

? Maybe I'd be using something extension functions to add similar behavior? I'm also not sure how I'd do something like

customSourceSetCompile

in

kotlin-script-gradle

, and am curious what the solution is.

@pawel.barszcz I am just using the default Gradle wrapper in IntelliJ

also, in 0.8 is there some other way to use the gradle ext than this?

val ext = (this as HasConvention).convention.extraProperties

@bamboo Does v4 of gradle not include

org/gradle/script/lang/kotlin/KotlinDependencyHandler

by default??

I mean, it is no longer necessary for just enabling Kotlin build script support

@bamboo Hi. Still can't seem to get publishing to work properly when following the manual. Manual's

publishing {
    publications {
        mavenJava(MavenPublication) {
            from(components.java)
        }
    }
}

results in "specif constructor, MavenPublication doesn't have companion object" and "mavenJava()" being unresolved reference It does compile if i replace it with

publishing {
    publications {
        create<MavenPublication>("mavenJava"){
            from(components["java"])
        }
    }
}

though. I don't get why it works on way and not the other?

@Czar I had problems with

java

being not recognised, finally I manage to do this in following way:

configure<JavaPluginConvention> {
    sourceSets[SourceSet.MAIN_SOURCE_SET_NAME].java {
        srcDir("src/main/kotlin")
    }
}

Will anyone at Gradle be at Kotlin Conf as a speaker to talk about GSK?

I'm trying to translate an existing Gradle plugin to Kotlin (well, several related plugins, actually). They include methods which take Groovy Closure objects. How can I call such a method from elsewhere in Kotlin? Do I need to overload such methods with versions which use Gradle's Action<T> interface, and pass Kotlin lambdas to that? I'm not sure that can work, given that some of the Closures expect multiple arguments. Or is there some way to wrap a Kotlin lambda / anonymous fun as a Closure?

@hughg Generally you want Action<T> afaik. But which closures expect more than 1 parameter? Are they closures executed by your plugin, or by Gradle?

i am using 3.5 and when I open the project built by gradle idea, everything in build.gradle.kts is red for me. I had to use direct import in idea to make it happy

my goal was to use kts with proper IDE support.

hello everyone! how would a custom configuration be added to

build.gradle.kts

? For reference this is what it can done for the Groovy version configurations { integrationTestCompile { extendsFrom testCompile } integrationTestRuntime { extendsFrom integrationTestCompile, testRuntime } functionalTestCompile { extendsFrom compile } functionalTestRuntime { extendsFrom runtime } } dependencies { functionalTestCompile “org.jetbrains.kotlin:kotlin-test-junit:$kotlinVersion” functionalTestCompile “org.codehaus.griffon:griffon-core-test:$griffonVersion” functionalTestCompile “org.codehaus.griffon:griffon-javafx-test:$griffonVersion” } sourceSets { integrationTest { kotlin.srcDirs file(‘src/integration-test/kotlin’) compileClasspath += sourceSets.main.output runtimeClasspath += compileClasspath } functionalTest { kotlin.srcDirs file(‘src/functional-test/kotlin’) compileClasspath += sourceSets.main.output runtimeClasspath += compileClasspath } } idea { module { scopes.TEST.plus += [configurations.integrationTestCompile] scopes.TEST.plus += [configurations.integrationTestRuntime] testSourceDirs += sourceSets.integrationTest.allSource.srcDirs scopes.TEST.plus += [configurations.functionalTestCompile] scopes.TEST.plus += [configurations.functionalTestRuntime] testSourceDirs += sourceSets.functionalTest.allSource.srcDirs } }

We see a lot of warnings like that in our Spring Gradle build :

getting this

Unsupported major.minor version 52.0

anyone using the kotlin for their gradle scripts? anyone recommend jumping in or holding off?

@sdeleuze please do raise a bug on the Kotlin YT, I have seen in the past but it would usually go away after the file type checked

Wondering what happened to the GSK PR I submitted. Last time I looked it appeared I had broken the build despite adding some documentation 💀.

The spring boot plugin hijacks dependency resolution in the most annoying way making it incredibly painful to try to force your own version of any dependency; in my experience.

any way to apply plugin: ‘kotlin-android’ in all modules?

I'm going to have a hard time getting over changing what I've been calling this project. I've been using GSK for 4 months now. Can we use GKD now?

Hello, is there anyone who got everything set up already (including IDEA support) to build a project with Gradle Script Kotlin? I got a few questions regarding the IDEA support, that's why I'm asking. My problem is actually that IDEA doesn't recognise that the project I'm working on (no matter which one) is a Gradle Script Kotlin based one. It doesn't offer me all of the new features they mentioned in the blog post, but instead "offers" me to add Kotlin support to my project, which actually fails if I press Okay because it can't find build.gradle (which isn't present when using GSK). There is nothing wrong with the code, I can build everything from the command line without any problems, but I can't get the syntax highlighting and stuff to work. I tried it with both IDEA CE/UE and various versions of the Kotlin Plugin.