@sdeleuze the latest Kotlin libraries required by gradle-script-kotlin are incompatible with the stable Kotlin release

With 0.7.0, I tried using the publishing plugin like this:

val publishing: NamedDomainObjectContainer<Publication> by extensions
publishing {
     "Module"(MavenPublication::class) {
        // more code here
    }
}

but I get this error:

Element 'publishing' of type 'org.gradle.api.publish.internal.DefaultPublishingExtension_Decorated' from container 'org.gradle.api.internal.plugins.DefaultConvention@260e45a' cannot be cast to 'org.gradle.api.NamedDomainObjectContainer'

Am I doing something wrong, or is this not supported yet?

As far as I understand, it’s only IDE showing errors, it builds and imports into IDE just fine, no?

It may not be optimized. Intellij takes a while to re-resolve all of the dependencies

When I import the project in Idea I have this error:

In multi-module projects, when you add

buildscript { dependencies { classpath(...) }}

in the root project, it is not used in sub-projects, neither in the IDE nor on the command line. This means that as it stands now, I have to repeat buildscript blocks with repository configurations, dependencies and version numbers in all projects where external plugins are applied. Is this a limitation that will go away before 1.0?

Hey @bamboo, I just started using

kotlin-gradle-script

. Is there going to be a better way to configure plugin DSLs, other than

configure<SomePluginExtension> { … }

?

Likely because no

kotlin-runtime in the classpath

@bamboo Do you need to use the EAP to make GSK work correctly?

For now, just disable the

Create Module for each SourceSet

option when importing

In the intellij Logs I'm getting a lot of log messages like this:

2017-02-21 16:11:08,981 [ 177485]   WARN - finder.JvmIDEVirtualFileFinder - There are 3 classes with same fqName: kotlin/io/FilesKt__FilePathComponentsKt found.

Some times ago we discussed about a documentation page to show Gradle Groovy -> Kotlin equivalence, is there such doc or wiki page available somewhere ?

@bamboo I've since had someone else import this project and they are having the same methods not getting resolved.

In any case, it’s better to avoid changing files in-place

Will GSK 0.8.0 work with 1.1-rc-91?

But it if I want to omit create it doesn’t work (extension function for string not found)

@bamboo I'm not sure if this is a limitation of gradle or kotlin:

@get:Input
    override val configuration: CodegenConfigurator by lazy { project.extensions.getByType(CodegenConfigurator::class.java) }

This throws an exception because:

Could not add entry ':PlexxiSwagger:Spec:swagger' to cache taskHistory.bin (/Users/jonathanleitschuh/work/git/plexxicontrol/.gradle/3.5-20170217174236+0000/taskHistory/taskHistory.bin).
> Unable to store task input properties. Property 'configuration' with value 'io.swagger.codegen.config.CodegenConfigurator_Decorated@735e4fd' cannot be serialized.

I know that the undecorated

CodegenConfigurator

is serializable because I made it so that it was: https://github.com/swagger-api/swagger-codegen/blob/master/modules/swagger-codegen/src/main/java/io/swagger/codegen/config/CodegenConfigurator.java#L38 Is this because of the extensions plugin?

Currently it’s failing with

unable to compile script

error

Using the interface

HasConvention

seems ugly given that there's a javadoc on it that says that its not going to stick around: https://github.com/JLLeitschuh/ktlint-gradle/blob/master/src/main/kotlin/org/jlleitschuh/gradle/ktlint/KtLintPlugin.kt#L37-L40 However, the GSK build uses the same thing; https://github.com/gradle/gradle-script-kotlin/blob/master/build.gradle.kts#L115-L117 I'm assuming if there was a better way you'd be doing it. Is there a way that plugins are supposed to consume the kotlin plugin's source set?

/**
 * Demarcates objects that expose a convention.
 *
 * Convention objects aren't going to be around forever, so this is a temporary interface.
 */
public interface HasConvention {

And why does the

"ktlintPlugin"

string not work with

apply

?

@bamboo Wow, DSL is much cleaner now, works fine for my project (but required IDE restart to enable syntax highlighting). The only thing that looks unnatural and confusing is workaround with

pluginBundle

and

gradlePlugin

extensions:

gradlePlugin {
    (plugins) {
        “pluginName" { /* plugin config */ }
    }
}

Anyway, good job!

I tried the new

plugins { }

syntax but declaring

org.jetbrains.kotlin.plugin.spring

don’t work (plugin not taken in account).

I’ve noticed that any time I add a plugin, I have to restart IntelliJ to get it working.

huh this seems odd - how come the build scan plugin looks like:

buildScan {
  setLicenseAgree("yes")
  setLicenseAgreementUrl(”<https://gradle.com/terms-of-service%22|https://gradle.com/terms-of-service">)

rather than

buildScan {
  licenseAgree = "yes"
  licenseAgreementUrl = “<https://gradle.com/terms-of-service>”

even though the methods seem to fit the right signature for setters -

public void setLicenseAgreementUrl(String var1)

@bamboo Do you have something on your roadmap to fix the “I have to restart IDEA after some changes to my

build.gradle.kts

to make it works” issue that various users (including me) reported?

@Chris Miller You need to use the task

gskGenerateAccessors

to figure out what code you need for that plugin.

How do I change the dependency direction between

compileKotlin

and

compileJava

tasks in gradle? I try this

compileJava.dependsOn.remove(compileKotlin)
compileKotlin.dependsOn(compileJava)

but I am still getting the error

Circular dependency between the following tasks:
:backend:compileJava
\--- :backend:compileKotlin
     \--- :backend:compileJava (*)

@spierce7 Gradle Script Kotlin perceived performance is quite bad because of https://github.com/gradle/gradle-script-kotlin/issues/249, should be fixed in 0.9

@timriemer

import org.jetbrains.kotlin.gradle.tasks.KotlinCompile
....
tasks.withType<KotlinCompile> {
    kotlinOptions {
        jvmTarget = JavaVersion.VERSION_1_8.toString()
    }
}