hi what would you recommend to pass parameters to a task

You can write a Gradle plugin that does everything instead and then you would just need to apply that plugin, not very recommended

hi there - I can't clarify the behavior of

buildSrc/build.gradle.kts

- does it affects onto main

build.gradle.kts

? because when I add

buildSrc/build.gradle.kts

and try to define some dependencies for my plugin - main file becomes "red"

I have a question about maven

what is "Replacing default-compile as it is treated specially by maven" supposed to mean

Hi, I got problem with configuring plugin extension. I can only configure it using configure function with plugin extension type parameter. When i use it like kotlin extension function gradle shows errors. I am using latest gradle version.

Is there a kotlin equivalent for creating a simple task without using the (IMHO unintuitive) doLast syntax?

task helloworld << {
    println("hello world")
}

How does one use the

internal

keyword inside the same module for say

integrationTests

(eg. as per the above definition it can be used across

main

and

unit

in the same module)?

Hey guys quick question. I'm separated my gradle dependencies into a kotlin file using buildSrc and kotlin plugin. It works fine. Downloads the dependencies properly and everything. But once I invalidate caches, it no longer works. Is there something I'm missing?

1.0-RC6 Gradle Kotlin DSL 1.0 RC6 Release Notes Gradle Kotlin DSL 1.0 RC6 brings Kotlin 1.2.61, support for configuration avoidance, a Gradle API decorated for Kotlin, enhanced IntelliJ IDEA integration, lots of DSL polish and bug fixes. At the same time the IntelliJ IDEA Kotlin Plugin fixed important build script editing related issues. It is recommended for everyone to upgrade to the latest and greatest. This release contains potential breaking changes, see below. v1.0-RC6 is included in Gradle...

Is such version definition is ideomatic? https://github.com/Heapy/tgto/blob/master/build.gradle.kts#L10-L26 Maybe there are some more concise way to retrieve versions?

I am using the following configuration in a

build.gradle.kts

with Kotlin 1.2.61 and Gradle wrapper 4.10.1:

buildscript {
    repositories {
        maven("<https://dl.bintray.com/kotlin/kotlin-dev>")
    }
}

repositories {
    maven("<https://dl.bintray.com/kotlin/kotlin-dev>")
}

plugins {
    id("org.gradle.kotlin.kotlin-dsl") version "0.18.3"
}

When I try to increase the version of

kotlin-dsl

to f.e.

0.18.4

or the latest

0.19.5

I get the following error:

Plugin [id: 'org.gradle.kotlin.kotlin-dsl', version: '0.18.4'] 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 'org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:0.18.4')
  Searched in the following repositories:
    Gradle Central Plugin Repository

What maven repository is missing here? Or, which combination of Kotlin and kotlin-dsl should work?

Also, is there a Kotlin DSL equivalent for excluding transitive dependencies for a particular configuration? https://docs.gradle.org/current/userguide/managing_transitive_dependencies.html#example_excluding_transitive_dependency_for_a_particular_configuration The migration guide seems to imply it should be possible: https://guides.gradle.org/migrating-build-logic-from-groovy-to-kotlin/#configurations-and-dependencies ...but when I try:

configurations {
	testImplementation {

	}
}

...I get:

Script compilation error:

  Line 21: 	testImplementation {
            ^ Unresolved reference. None of the following candidates is applicable because of receiver type mismatch: 
                public inline fun <T : ModuleDependency> DependencyHandler.testImplementation(dependency: TypeVariable(T), dependencyConfiguration: TypeVariable(T).() -> Unit): TypeVariable(T) defined in org.gradle.kotlin.dsl
                public fun DependencyHandler.testImplementation(dependencyNotation: Any): Dependency? defined in org.gradle.kotlin.dsl
                public fun DependencyHandler.testImplementation(group: String, name: String, version: String? = ..., configuration: String? = ..., classifier: String? = ..., ext: String? = ...): ExternalModuleDependency defined in org.gradle.kotlin.dsl
                public inline fun DependencyHandler.testImplementation(group: String, name: String, version: String? = ..., configuration: String? = ..., classifier: String? = ..., ext: String? = ..., dependencyConfiguration: ExternalModuleDependency.() -> Unit): ExternalModuleDependency defined in org.gradle.kotlin.dsl
                public inline fun DependencyHandler.testImplementation(dependencyNotation: String, dependencyConfiguration: ExternalModuleDependency.() -> Unit): ExternalModuleDependency defined in org.gradle.kotlin.dsl

1 error

I have question regarding dependency resolution for plugins. I have the following situation: • A plugin (https://github.com/Stvad/kask-gradle-plugin) that depends on the library I’ve developed - https://github.com/Stvad/kask • The library is build/served by https://jitpack.io. It’s presented as a maven repo -

maven(url = "<https://jitpack.io>")

• The plugin is published on the gradle plugin portal. When I’m trying to use the plugin though I’m facing several problems: • If I just use the plugin via

id("org.stvad.kask") version "0.1.1"

entry in

plugins

section, the project fails initial configuration, with the following error (basically gradle is looking for dependency in the wrong place and not finding it):

Could not find com.github.Stvad:kask:-SNAPSHOT.
Searched in the following locations:
  - file:/Users/sitalov/.gradle/caches/4.10/embedded-kotlin-repo-1.2.60-2/repo/com/github/Stvad/kask/-SNAPSHOT/maven-metadata.xml
  - file:/Users/sitalov/.gradle/caches/4.10/embedded-kotlin-repo-1.2.60-2/repo/com/github/Stvad/kask/-SNAPSHOT/kask--SNAPSHOT.jar
  - <https://plugins.gradle.org/m2/com/github/Stvad/kask/-SNAPSHOT/maven-metadata.xml>
  - <https://plugins.gradle.org/m2/com/github/Stvad/kask/-SNAPSHOT/kask--SNAPSHOT.pom>
  - <https://plugins.gradle.org/m2/com/github/Stvad/kask/-SNAPSHOT/kask--SNAPSHOT.jar>
Required by:
    project : > org.stvad.kask:org.stvad.kask.gradle.plugin:0.1.1 > org.stvad:kask-gradle-plugin:0.1.1

I can work around that problem by adding the following configuration in the project settings:

kotlin
pluginManagement {
    repositories {
        gradlePluginPortal()
        maven(url = "<https://jitpack.io>")
    }
}

Which, works, I guess =/, but I’m surprised I have to do this. But after that I have more troubles - my understanding was that plugin dependencies should be transitively available to the project using that plugin. But it does not seem to work for me - in order to make the aforementioned library usable from the project that is applying the plugin, I had to explicitly declare repository and dependency configurations. Which means that to use the plugin properly user would have to: 1) apply it; 2) change plugin repo configuration; 3) add new repo to the project; 4) add explicit library dependency to the project. Which seems rather cumbersome. What I want to achieve is situation when a user of a plugin just needs to apply it and does not have to worry about dependency any dependency declarations. I’d appreciate your advice on how I can achieve that!

Related: We’d like to help plugin authors provide Kotlin DSL samples. If you’re on this list (https://github.com/gradle/gradle/issues/6790) or want to me, also contact me or Paul on the Gradle team!

@eriwen What about

<http://plugins.gradle.org|plugins.gradle.org>

? Is there any issue about supporting of Kotlin DSL snippets?

Hi all, I’ve upgraded my build to use 1.2.70, and I have a strange error:

Caused by: java.lang.ClassNotFoundException: org.gradle.api.attributes.HasAttributes

guys, after updating to 1.2.70

Sorry if it's a stupid question, but how can I specify, in my

build.gradle.kts

, that I want to target JVM 10?

Hi, does anyone knows the reason / workaround for this issue? -> https://youtrack.jetbrains.net/issue/KT-26834

Required by:
      project :example-v8
   > Unable to find a matching variant of project :karibu-dsl-v8:
       - Variant 'apiElements':
           - Found org.gradle.usage 'java-api' but wasn't required.
           - Required org.jetbrains.kotlin.platform.type 'common' and found incompatible value 'jvm'.
       - Variant 'runtimeElements':
           - Found org.gradle.usage 'java-runtime-jars' but wasn't required.
           - Required org.jetbrains.kotlin.platform.type 'common' and found incompatible value 'jvm'.

when using kotlin 1.2.70 and gradle

Does anyone have an example of a real world multi-file Kotlin based gradle build? Especially with using plugins in the non-

build.gradle.kts

files? I'm a complete newbie to the Kotlin DSL and struggling with getting plugins to work in a

foo.gradle.kts

file, and it would be nice to see how others have done it.

does anyone know where hte gradle docs are for dynamic version declarations ? i found the docs for how dependency locking works: https://docs.gradle.org/4.8/userguide/dependency_locking.html but i have no ideal what other than

+

and that range syntax

[5,)

is supported by gradle

you can provide more strongly-typed

ext

variables by adding extension methods that cast the values

It works if I put them in the

buildSrc

folder, but I still have red errors in the IDE. I have to sync the project, and then open the buildSrc file again for the IDE error to disappear. Is that a known issue?

Actually, I'm finding that I have to duplicate my kotlin version declaration. I have to put it in

buildSrc

, but also, the

buildscript

block so that I can add the kotlin plugin to the classpath. Is there a way around this?

Upgraded to stable Android Studio 3.2.0 yesterday, and all my .kts scripts are in red. Tried to clean the caches and restarted AS few times, tried to remove

.idea

and all `.iml` files and reimport the project, nothing helps. build.gradle.kts files are still all in red. Building is still working properly btw. I saw the answer: https://kotlinlang.slack.com/archives/C19FD9681/p1519224896000437?thread_ts=1519133138.000031&cid=C19FD9681 also saw that this bug in AS is marked as fixed: https://youtrack.jetbrains.com/issue/KT-20521 It just soooo frustrating to work with dsl, just asking for some workaround here, maybe i’m missing some simple tweak?

For Android, I think you still need to use the buildscript+classpath approach. Settings.gradle.kts + pluginManagement didn’t really work well for me the last time I tried. Debug builds work fine. But building for release always throws an exception. Something about implicit compile/implementation configuration or stuff along that line

Are you forced to have the

resolutionStrategy

block in

settings.gradle.kts

?