Hi, I am trying to get off the ground with a Dropwizard skeleton building and running with Gradle via the Kotlin DSL. I want to run up the application using a common approach such as: https://stackoverflow.com/questions/28610015/run-main-method-using-gradle-run-task My run block in Intellij is giving me hassle as it does not want to recognise the args as in the link above. It also seems to think the run {} is some funky Kotlin function. Any ideas please?

Current issue

Caused by: org.gradle.cache.CacheOpenException: Could not open cache directory aat8l8gx46xy6a1lqc8xd1ny9 (/home/jakob/.gradle/caches/4.3.1/gradle-kotlin-dsl/aat8l8gx46xy6a1lqc8xd1ny9).
	at org.gradle.cache.internal.DefaultPersistentDirectoryStore.open(DefaultPersistentDirectoryStore.java:61)
	at org.gradle.cache.internal.DefaultPersistentDirectoryStore.open(DefaultPersistentDirectoryStore.java:32)
	at org.gradle.cache.internal.DefaultCacheFactory.doOpen(DefaultCacheFactory.java:90)
	at org.gradle.cache.internal.DefaultCacheFactory.open(DefaultCacheFactory.java:64)
	at org.gradle.cache.internal.DefaultCacheRepository$PersistentCacheBuilder.open(DefaultCacheRepository.java:123)
	at org.gradle.kotlin.dsl.cache.ScriptCache.cacheDirFor(ScriptCache.kt:51)
	at org.gradle.kotlin.dsl.cache.ScriptCache.cacheDirFor$default(ScriptCache.kt:43)
	at org.gradle.kotlin.dsl.provider.CachingKotlinCompiler.cacheDirFor(CachingKotlinCompiler.kt:170)
	at org.gradle.kotlin.dsl.provider.CachingKotlinCompiler.compileScript(CachingKotlinCompiler.kt:131)
	at org.gradle.kotlin.dsl.provider.CachingKotlinCompiler.compileBuildScript(CachingKotlinCompiler.kt:111)
	at org.gradle.kotlin.dsl.provider.KotlinBuildScriptCompiler.compileScriptFile(KotlinBuildScriptCompiler.kt:239)
	at org.gradle.kotlin.dsl.provider.KotlinBuildScriptCompiler.executeScriptBodyOn(KotlinBuildScriptCompiler.kt:111)
	at org.gradle.kotlin.dsl.provider.KotlinBuildScriptCompiler.prepareAndExecuteScriptBodyOn(KotlinBuildScriptCompiler.kt:105)
	at org.gradle.kotlin.dsl.provider.KotlinBuildScriptCompiler.access$prepareAndExecuteScriptBodyOn(KotlinBuildScriptCompiler.kt:48)
	at org.gradle.kotlin.dsl.provider.KotlinBuildScriptCompiler$compileTopLevelScript$1.invoke(KotlinBuildScriptCompiler.kt:88)
	at org.gradle.kotlin.dsl.provider.KotlinBuildScriptCompiler$compileTopLevelScript$1.invoke(KotlinBuildScriptCompiler.kt:48)
	at org.gradle.kotlin.dsl.provider.KotlinScriptPlugin.apply(KotlinScriptPlugin.kt:48)
	at org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:61)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
	at org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:58)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:41)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26)
	at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:64)
	... 84 more

Another differnet issue

e: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter

When using java9

All the documentation is out of date for everything, I have spent about 2 days trying to get everything to just work and its not, its super frustrating

Hi, guys! When (approximately) are you planing on releasing kotlin DSL 1.0 ? I understand that usually it is a bad question to ask, but I need a very rough approximation of how close you think you are to the 1.0 point. 3 months? A year? Thanks in advance !

buildscript { ext.kotlin_version = '1.1.60' ext.tornadofx_version = '1.7.8' repositories { mavenCentral() jcenter() } dependencies { classpath "org.jetbrains.kotlinkotlin gradle plugin$kotlin_version" classpath 'com.github.jengelman.gradle.pluginsshadow1.2.3' classpath 'no.tornadofxlauncher gradle plugin1.0.16' } } apply plugin: 'kotlin' apply plugin: 'application' apply plugin: 'com.github.johnrengelman.shadow' apply plugin: 'no.tornado.fxlauncher' repositories { mavenLocal() mavenCentral() } dependencies { compile "org.jetbrains.kotlinkotlin stdlib$kotlin_version" compile "no.tornadotornadofx$tornadofx_version" compile 'org.controlsfxcontrolsfx8.40.12' compile "org.apache.commonscommons dbcp22.1.1" compile 'com.google.guavaguava23.5-jre' }

Okay sorry i was not aware

I am not exactly sure how

HasImplicitReceiver

annotation works on the

Action

interface but it seems to workin build.gradle.kts and doesn't seem to work in *.kt files in buildSrc. I have to explicitly cast to the receiver:

private fun KotlinBuildScript.setupIvyRepository() {
  plugins.apply("org.gradle.ivy-publish")
  val conf: org.gradle.api.publish.PublishingExtension.() -> Unit = {
    repositories {
      this as RepositoryHandler
      ivy {
        this as IvyArtifactRepository
        url = URI("file:////C:/Temp/ivy.local")
        layout("pattern") {
          this as IvyPatternRepositoryLayout
          ivy("[module]/[revision]/ivy.xml")
          artifact("[module]/[revision]/[artifact]-[type].[ext]")
        }
      }
    }
  }
  extensions.configure("publishing", conf)
}

After updating my project to 1.2.0, I still have transitive deps pulling in 1.1.x. Do I need to force the correct kotlin version with a

resolutionStrategy

or is there a more elegant approach?

switching from the gradle plugin version 1.1.51 to 1.2.0 i get the following error

Could not find Kotlin Compiler classpath. Please specify compileKotlin.compilerClasspath

. Anybody know what is going on?

is there a way to force all kotlin deps to

1.2.0

easily?

We haven’t updated the master branch yet because Gradle 4.4 GA hasn’t been released

Are init scripts also supported with .kts extensions or does that have wait. I remember seeing the open ticket for settings.gradle.kts support but I don't specifically remember there being a ticket to support -I init.gradle.kts files.

I created a gradle plugin in kotlin but I cant seem to get it working. When the I compile the plugin to a jar and use it in another project to test it I get

Build cache type 'com.drost.buildcache.minio.MinioPlugin' has not been registered.

I have the gradle-plugins file in meta inf with

implementation-class=com.drost.buildcache.minio.MinioPlugin

which I set with the

java-gradle-plugin

Hey, with gradle kotlin scripts, one of the things that I find a bit toooo noisy compared to plain groovy gradle scripts, is the necessity to put in

${property("foo")}

inside dependencies definitions, i.e.,

compile("com.google.protobuf:protobuf-java:${property("protobufVersion")}")

I know there is another way of defining the var inside the kts file,

var foo="1.2"

then using

$foo

inside the dependency definition. The latter being more "groovy" like (without the var definition). Is there no shorter way of expressing this?

What is the replacement for tasks.getting in Gradle 4.4?

the

tasks.getting

is working for me for all

val dokka by tasks.getting

and

tasks { val dokka by getting(DokkaTask::class) }

, and

val dokka by tasks.getting(DokkaTask::class)

Receiving this error after updating Gradle to 4.4: e: Kotlin home does not exist or is not a directory: :compileKotlin2Js FAILED

project(":child:grandchild") {
	plugins {
		id("war")
		id("org.springframework.boot")
	}
	dependencies {
		providedRuntime("org.springframework.boot:spring-boot-starter-tomcat")
		//...
	}
	//...
}

gives me unresolved reference:

providedRuntime

Any ideas?

providedRuntime

probably should be within a

dependencies

block.

Yes please add it, I’ll triage it right away

or even:

tasks {
    "bower" {
        dependsOn("gulp_bower")
    }
}

I’m using

kotlin.copyClassesToJavaOutput = true

and it works well in our setup, but it causes tests to run twice when using the gradle test runner

This change https://github.com/JetBrains/kotlin/commit/5ce514bd42a8e8cb2afac99ea20bc359a4222951 introduces a regression that prevent us to generate the Dokka documentation for Kotlin code without using Java code since we were using

sourceDirs = files(subprojects.collect { project -> project.sourceSets.main.kotlin.srcDirs })

. What can I use to get only the Kotlin source dirs ?

i dont think that is what is causing it - there is a

build.gradle.kts

in the directory that can't be compiled.

can you please elaborate @bamboo

is there a way to suppress

Using Kotlin incremental compilation

info?

Hey guys, I don’t get kotlin-dsl running. 😕 For testing I’ve created a simple hello tasks like that:

task("Hello") {
  println("Hello World")
}

This works. Now I wanted to map this to my android project. I’ve updated the script to:

buildscript {
  repositories {
    jcenter()
    google()
  }

  dependencies {
    classpath("com.android.tools.build:gradle:3.0.1")
  }
}

apply {
  plugin("com.android.application")
}

android {
  compileSdkVersion("26")
}

But if I run it I get:

build.gradle.kts181: Unresolved reference: android

build.gradle.kts193: Unresolved reference: compileSdkVersion

What I’m doing wrong? I’ve already checked out the samples. With the hello-android I don’t have that issue 😕

compile(kotlin("stdlib", "1.2.0"))

won't help, you'll have to specify it for all stdlib variants if you want to do it like that.

gradle.properties

is easier, IMO.

yup, true, you do not have to specify

kotlinVersion

for dependencies in this case, I do though, because project I copied this from is a lib, and if I don't the version is not properly resolved on the project which is depending on my lib.