how the heck do you use

bootJar

with the kotlin dsl?

Is there a way to change the artifact name for a module in a Gradle multi module project via Kotlin DSL?

How is a Kotlin multi-platform library published via Kotlin DSL?

Hi guys, is it possible to prepopulate a db (realm or room) within a gradle task? I have a table from db in json or csv that I need to parse to deliver apk with this data. Thanks!

just move that one out of the ext block as well?

Hello folks! Is there any problem with

gradle-completion

and Kotlin DSL Gradle scripts? I see it doesn't quite "discover" (read: auto-completes) all the tasks correctly...

i tried every method i could think of to get to a closure created under dependencies.ext by a gradle plugin written in groovy that I have to use for this application

@bamboo @eskatos Congratulations on a 1.0 RC! It's been awesome watching this project evolve over the past year and a half. This project has come so far and it really is awesome to work with.

Yay!!! Go Gradle! I'm fiercely advocating kotlin-dsl at work, we've already rewritten some scripts several months back, and couldn't have been happier about it. I'm personally working towards 100% kotlin-dsl builds 🙂

Are we able to create

NamedObjectDomainCollection

objects in our plugins or is there no way to instantiate one without using internal API'S?

what's the best way to set variables across a multi module project. I'm using spring boot's dependencyManager since gradle's IMPROVED_POM_SUPPORT apparently doesn't work the same way as maven's BOMs and I need to set the same version for the bom across all modules.

Execution failed for task ':buildSrc:compileKotlin'.

Could not resolve all files for configuration ':buildSrc:kotlinCompilerPluginClasspath'.

> Could not find org.jetbrains.kotlin:kotlin-scripting-compiler-embeddable:1.2.60. Searched in the following locations: file:/home/bernhard/.gradle/caches/4.10-rc-1/embedded-kotlin-repo-1.2.60-2/repo/org/jetbrains/kotlin/kotlin-scripting-compiler-embeddable/1.2.60/kotlin-scripting-compiler-embeddable-1.2.60.jar Required by: project :buildSrc > Could not find org.jetbrains.kotlin:kotlin-sam-with-receiver:1.2.60. Required by: project :buildSrc

What is the kotlin gradle dsl equivalent to

mainClassName

in

application

plugin?

Hi there, please help me understand how to configure

processResources

correctly. What I’m trying to do is: I have a file:

src/main/res/xml/file.xml

which has a string like

<external-path name="my_images" path="Android/data/{$appId}/files/Pictures/" />

. Now I’m trying to replace appId token in gradle build script as follows:

tasks {
    withType<ProcessResources> {
        filesMatching("${projectDir}/src/main/res/xml/file.xml") {
            val tokens = mapOf("appId" to "myApplicationId")
            expand(tokens)
        }
        outputs.upToDateWhen { false }
    }
}

But that seems not working. Build finishes without errors, but if I open that xml file after artifact is produced, the template is not fulfilled. I spend on this a almost a day, please help me understand what’s wrong here.

This is probably not the right channel/Slack, but what's the difference between an implementation and a runtimeOnly dependency?

Any suggestions on where to look/read/ask/learn how to create gradle dependencies that are not file-based. Examples: tasks that produce docker images, aws resources, send emails etc. Things with expensive or non-idempotent side effects that should only be done if out of date.

In terms of the long term objectives of gradle, once 1.0 is released, will kotlin gradle kotlin dsl be the 'recommended' language for a build in gradle? For instance will we see more example being done in kotlin like google android has done for their examples?

@danny re: upToDate etc .. each case ends up eventually with some kind of explanation (it is 'just software') -- but each time its different, when it doesnt work how I expect it will it can take hours or days to debug or give up on. Its not only upToDate, problems arise with transitive task dependencies, cached statuses, entirely skipped tasks or tasks reran unexpectedly ... For File based tasks, its tricky enough to uncover the implicit 'conventions' -- but they do seem to be much more consistent behaviour. I believe this is inherent in much of the lifecycle rules -- the history of build systems is very much about pushing files around its difficult (and not necessarily better) to be fully agnostic about what dependency really means in the domain. But it does make it harder to do non-files based dependencies. Example: there is no mechanism I am aware of that can be cleanly used to provide the equivalent of a file timestamp and content/checksum for non-file 'resources' -- as a 'resource' they are not modeled at all, so one has to go to the task abstraction to work around holes in the metadata. I have had some luck by persisting a 'status' file for each non-file type resource dependency, toudhing it (and changing its contents) needed -- but there is no hooks I know of to know when the checks need to be rerun or when gradle is looking at them. Very deeply hidden (intentionally). So I was wondering, if in Kotlin DSL maybe there is a better way to manage non-file dependencies. SUch as creating a derived Dependency object that behaves 'like a file' ? Just speculating.

where's the getting started docs, or whatever? for gradle.build.kts

Are typed extensions or named objects working in the lastet kotlin-dsl ? No matter what I do (so far) Im getting the Accessors0.kt file generating accessors for extension objects written in Kotlin with "Any" type Like this: /** * Retrieves the [report][nexstra.client.workflow.RunReportSteps.Parameters] extension. * *

report

is not accessible in a type safe way because: * -

nexstra.client.workflow.RunReportSteps.Parameters

is not available */ val org.gradle.api.Project.`report`: Any get() = (this as org.gradle.api.plugins.ExtensionAware).extensions.getByName("report")

@trevjones what is "topLevel"?

wtf...

Task ':publishPlugins' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Publishing plugin com.xenoterracide.gradle.sem-ver version 0.5.1
Publishing plugin com.xenoterracide.gradle.code-quality version 0.5.1
Publishing plugin com.xenoterracide.gradle.java-lib version 0.5.1
Publishing artifact build/libs/pluginbundle-0.5.1.jar
Publishing build/libs/pluginbundle-0.5.1.jar to <https://s3.amazonaws.com/plugins-artifacts.gradle.org/gradle.plugin.com.xenoterracide.gradle/pluginbundle/0.5.1/a1d6eaae70cfb8069c7dda4c4055da890d5c1ab3c9643b158822bb09161451e8/pluginbundle-0.5.1.jar?x-amz-acl=public-read&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20180822T213423Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3600&X-Amz-Credential=AKIAJSORG5G77OJXTM7Q%2F20180822%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=98d8ce98a557d4684baf32d27703194aebc063f9176e5a2ba7fc862543b1ce51>
Publishing artifact build/libs/pluginbundle-0.5.1-sources.jar
Publishing build/libs/pluginbundle-0.5.1-sources.jar to <https://s3.amazonaws.com/plugins-artifacts.gradle.org/gradle.plugin.com.xenoterracide.gradle/pluginbundle/0.5.1/3d547bef2fdf8d2fd6e76fa441a24c1316333e8341b26f486731a09673dc1c6d/pluginbundle-0.5.1-sources.jar?x-amz-acl=public-read&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20180822T213423Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3600&X-Amz-Credential=AKIAJSORG5G77OJXTM7Q%2F20180822%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=4022becd4b0ad5abfb84a95a8c5bb7d6f9e97fa8a651f948eac279fd48bdc9e5>
Publishing artifact build/libs/pluginbundle-0.5.1-javadoc.jar
Publishing build/libs/pluginbundle-0.5.1-javadoc.jar to <https://s3.amazonaws.com/plugins-artifacts.gradle.org/gradle.plugin.com.xenoterracide.gradle/pluginbundle/0.5.1/5f9f7d8ee6faf3208dd9a7043ebdb76bb297f8c2a220c09b305829e33eee0cb1/pluginbundle-0.5.1-javadoc.jar?x-amz-acl=public-read&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20180822T213423Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3600&X-Amz-Credential=AKIAJSORG5G77OJXTM7Q%2F20180822%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=9988e5026b5d8602bd665b3dcfe603b2e027ac07dbcbf5d6d73abfb6610d2ba2>
Publishing artifact build/publish-generated-resources/pom.xml
Publishing build/publish-generated-resources/pom.xml to <https://s3.amazonaws.com/plugins-artifacts.gradle.org/gradle.plugin.com.xenoterracide.gradle/pluginbundle/0.5.1/5a90476c221b23cb954164c51d7eacb35d4aa47fd8a5b2cf8a2ed56b41274112/pluginbundle-0.5.1.pom?x-amz-acl=public-read&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20180822T213423Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3600&X-Amz-Credential=AKIAJSORG5G77OJXTM7Q%2F20180822%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=8b4a80f2c60090f0470cd9f9d808ff0ac68b22fedbb711b64e12921ec199cae8>
Activating plugin com.xenoterracide.gradle.sem-ver version 0.5.1
Activating plugin com.xenoterracide.gradle.code-quality version 0.5.1
Activating plugin com.xenoterracide.gradle.java-lib version 0.5.1

https://plugins.gradle.org/plugin/com.xenoterracide.gradle.java-lib/0.5.1

* What went wrong:
Plugin [id: 'com.xenoterracide.gradle.java-lib', version: '1.5.1'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'com.xenoterracide.gradle.java-lib:com.xenoterracide.gradle.java-lib.gradle.plugin:1.5.1')
  Searched in the following repositories:
    Gradle Central Plugin Repository

extra[“enableCrashlytics”] is not working in my new build.gradle.kts

@DALDEI https://docs.gradle.org/current/userguide/lazy_configuration.html is the official docs i think it makes it simpler to compose things together and not rely on configuration-time evaluation ordering

Hello #gradle Kotlin DSL enthusiasts! Are you interested in easy-ish contributions to Gradle/Kotlin DSL and recognition/Gradle swag? As you may know, Kotlin DSL 1.0 RC is here (https://blog.gradle.org/gradle-kotlin-dsl-release-candidate). We want to have Kotlin DSL equivalents for all our documentation samples, starting with the user manual (at docs.gradle.org). I have written instructions and guidelines in this GitHub issue (https://github.com/gradle/gradle/issues/6442) if you’re interested. Please consider contributing and coordinating/asking questions here or in Gradle Community Slack (https://gradle-community.slack.com/).

and not all of it can be blamed on the kotlin dsl, me thinks

Before I go off to stack overflow, can anyone think of a reason why my fatjar script isn't including anything from my /src/main/resources (but is including resources from other dependencies)?

jar{
	// required for building JAR files
	baseName = 'bascule'
	version = '0.0.1'
	manifest {
		attributes(
				'Main-Class': 'org.liamjd.bascule.MainKt'
		)
	}
	from('/src/main/resources') {
		include '*'
	}
	from { configurations.compile.collect { it.isDirectory() ? it : zipTree(it) } }
}

What is the canonical way to configure component in Kotlin Gradle DSL? So far I've come with following solution:

(components["main"] as KotlinNativeMainComponent).apply {
    outputKinds.set(listOf(OutputKind.EXECUTABLE))
}

but maybe there is a better way?