@cbeams: hi, I saw your talk "Writing Gradle Build Scripts in Kotlin" from the Gradle Summit 2016, very nice! I have one question: for the buildscript you use multiple-pass compilation to make stuff available in the rest of the script, why can't you use the same mechanism for applying plugins?

@memoizr: https://kotlinlang.slack.com/archives/gradle/p1471095813000191 Maybe this could help - https://github.com/gradle/gradle-script-kotlin/issues/103

closureOf<TypeOfYourClosure>{}

Trying to follow https://github.com/gradle/gradle-script-kotlin/tree/master/samples - I’m looking at the samples instructions (trying to run with

3.0-rc-2

) and cant download the latest kotlin plugin from https://teamcity.jetbrains.com/guestAuth/repository/download/bt345/832964:id/kotlin-plugin-1.1.0-dev-2091.zip

@mkobit, @bamboo: kotlin master branch builds expire with the time, unless pinned, so a permanent link to a build should be given with caution. Try this one, currently we use it for bootstrapping and it's pinned: https://teamcity.jetbrains.com/guestAuth/repository/download/bt345/837716:id/kotlin-plugin-1.1.0-dev-2222.zip

@gildor: thanks for that! It seems a bit clunky though.

@memoizr: Actually, as I know, this is issue of plugin, because plugin developer should implement not only Closure<T> configuration way, but also Action<T> configuration, that supported by Kotlin Gradle Scrips

Yeah the Maven plugin only has Closure for some reason.

Anyway, does any of you know about any open source project that is using a Kotlin build script already?

So, after much toiling, I managed to port one of my libraries to use a Kotlin Gradle build script. Here it is! https://github.com/memoizr/retro-optional/blob/master/build.gradle.kts

It uses the Jacoco plugin, Bintray and Maven. So that was fun.

I would be super grateful if I could get some feedback on how to make it better. I think it's pretty bad right now, so there should be plenty to suggest 😄

In particular, I struggled with the "licenses" block inside the "pom" block. I had no idea of how to get to that, so I created a micro DSL to write the POM XML. 🙂 surely there's a better way!

great job!

@dstarcev: thanks, let me know if you know of better ways of doing it. I'd love to get this looking as sexy as the groovy version can.

Which IDE do you use? Does it collapse the imports?

I'm using Intellij IDEA Community, and yes the imports are collapsed like in normal classes/files

autocompletion works, including the plugins.

To be honest, I much prefer explicit imports, as otherwise it might feel like magic (the "where did it come from?" effect)

I am going to try it in the nearest future

yeah it was a bit painful 😄

You may want to write an article on that

yeah that's the plan. But I want to get to know this very well so I can do it justice.

that's why I'm very keen on feedback 😄

@memoizr: the statically typed version would be

configure<JavaPluginConvention> {
    setSourceCompatibility(1.7)
    setTargetCompatibility(1.7)
}

Thanks, @ilya.gorbunov, I’ve updated the README to mention the new version

@bamboo: Thanks!

in 'normal' gradle projects I've got a

dependencies.gradle

file containing something like:

ext {
  jUnit = "junit:junit:4.12"
}

Then I can use it like:

apply from './dependencies.gradle`
dependencies {
  testCompile jUnit
}

How is this possible in Kotlin?

inside your

apply

block, specify the name of the file with

from("dependencies.gradle")