Reminder to star this issue as the way gradle handles this currently is hurting the ecosystem https://github.com/gradle/gradle/issues/16345

I really dislike this "There isn't Kotlin in the question, GTFO" attitude. Why do we even have a gradle channel then? At the end of the day we are all engineers together in the community, why not try to help each other out anyway? It's really disappointing to see. There are people here who do try to help and offer advice regardless and I commend and thank those people, but unfortunately I seem to notice more of the unhelpful attitude than the helpful one. This is not just limited to the gradle channel, I have seen the behaviour elsewhere as well.

still looking for help ☝️ . if there’s anything i can do to make the issue clearer please let me know

We are seeing this problem quite often now https://youtrack.jetbrains.com/issue/KT-48779#focus=Comments-27-5206280.0-0 This is a comment with more info and repository where it's reproducible (but kinda hard, it's not 100%, we're still investigating causes) ------------------- What i'am thinking of is a flag that would crash build process instead of using fallback It's important, because silent fallbacks degrade CI performance very badly, and is hard to look for: there is no API to get callbacks and add some alerting on it, so one should monitor build output for specific strings which is kinda meh.. --- Flag is just a flextape, what is really needed is meaningful and actionable information of why daemon can't compile; which is not always accessible, even /tmp/kotlin-daemon*.log can contain no valuable info at all ---- p.s. I'm ready to contribute such a flag if it will be considered good idea

I was trying to use

apply

, however it did not work

reposting as i’m getting a little desperate and not getting any answers. any help would be appreciated. i created an issue https://youtrack.jetbrains.com/issue/KT-48891. i’m uploading a sample project that allows you to easily recreate the problem

PROTIP: The green hammer in the IDE is an “I'm feeling lucky” construct and you shouldn't use it anyway. It best effort builds whatever it thinks you have currently focused in the IDE. Focused on a file? It builds that file's module. Focused on another module in the project view? It builds that module. Focused on nothing? It builds everything.

And in build.gradle.kts file!

Cross-posting because folks recommended me to: https://kotlinlang.slack.com/archives/C3SGXARS6/p1634934836023400

What are you guys doing for sourceCompatibility with Gradle builds and JDK 17 since Gradle doesn't support Java 17 yet?

I'd like to be able to run a script in node_modules/.bin using Gradle and kotlin("multiplatform") version 1.5.31. I can see that the npm dependency is downloaded and the script exists in

<rootDir>/build/js/packages/data-model/node_modules/.bin/tstl

, but can I create a Gradle task that executes

npx tstl

or similar in a nice way? I feel like I'm close. I see in

NpmProject

there's

fun useTool(...)

- but I can't figure out how to access the

NpmProject

from within a build.gradle.kts. https://github.com/JetBrains/kotlin/blob/0915dac1f9f0e435e85d6b0cf3d255da1fd9ece1/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/targets/js/npm/NpmProject.kt#L86 I also see there's a

NodeJsExec

- but I can't see how to get the required

KotlinJsCompilation

instance https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/targets/js/nodejs/NodeJsExec.kt

I am trying to exclude some classes from an android apk. These classes are located in the build folder. Exclude does not seem to work! Is there any sort of limitation/bug?

jcenter certificate was expired and wasn't renewed (or serving server was not updated)

image.png

I tried changing

gradlePluginPortal

to

mavenCentral

, works a little bit, but then fails with:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.5.21')
  Searched in the following repositories:
    MavenLocal(file:/home/arian/.m2/repository/)
    MavenRepo

jcenter is back with valid certificate

I'm adding a few vendored libs via

flatDir

, can I somehow also add the dependencies of these libs to gradle without copypasta?

Hello! When switching from Kotlin 1.5.31 to 1.6.0, my gradle script start throwing exception. I have function fun configuration(target: KotlinJvmTarget): Configuration { return target.project.configurations.getByName(target.defaultConfigurationName) } at getByName part it is throwing org.gradle.api.artifacts.UnknownConfigurationException: Configuration with name 'implJvmDefault' not found. How can i fix it?

I have a question about Gradle sourceSets. I am trying to find a good way to apply DDD patterns in my project, and I was thinking about how to encapsulate the different layers. My goal is to use the model where the domain code is on its own with zero dependencies except for stdlib, coroutines, and logging. Application layer depends on the domain code but also has almost zero external dependencies. And infra layer depends on both domain and application layers, and is what deals with talking to databases, message brokers, etc., so it has a number of those dependencies. So I was thinking that maybe I could use a single jar for a given application module (mapped to a bounded context). It would have a sourceSet each for the domain, application, and infrastrucuture layers, with the dependencies between them as described above. Code marked as

internal

in each layer should only be visible to other code in that layer (and its corresponding test sourceSet). Code outside of the module (jar) should only be able to see public code in the infrastructure layer. That is what comprises the public API for the whole jar file, and it is tiny. Just a couple of extension functions, interfaces, and classes. The compilation should result in only a single jar file. Is that something I can get working with sourceSets? Would JPMS modules be a better fit? I've never played around with JPMS, and I'm still learning Gradle. I know I can mostly achieve this by just extracting the layers into their own projects, but then it's hard to enforce the encapsulation because other projects can simply declare a dependency on those. I considered using a composite build but then I can't share dependencies or convention plugins between the components. We aren't a huge team, so it wouldn't be the end of the world, but if I can come up with a better solution then that would be ... better! Thanks a lot, Morgan

Do we need to add any extra dependencies to be able to use

java.lang.reflect.*

package in a Kotlin/Java library? I am able to access this package in the main "android-application" module but some isn't working in my Java-Library module. I have added the following dependencies in this library module

kotlin-stdlib

com.google.code.findbugs

moshi

,

retrofit

,

moshi-kotlin-codegen

Is adding a public class ABI change, causing a recompile in dependants?

I'm trying to use

CreateStartScripts

for a target in the JVM part of a multiplatform project. The usual setting classpath via

tasks.getByName("jar").outputs.files + configurations.getByName("runtimeClasspath")

does not work. Anyone know the right values? I've tried

classpath = tasks.getByName("jar").outputs.files +
      tasks.getByName("jvmJar").outputs.files +
      configurations.getByName("jvmRuntimeClasspath")

but it doesn't work. The script doesn't have the right classpath. Its missing the jar that is output in

build/libs

and it also seems to be missing some core stuff like "coroutines" that is defined in common. SOLVED, seems to work:

val backendJar by tasks.existing
  val backendRuntimeClasspath by configurations.existing
  classpath = files(backendJar, backendRuntimeClasspath)

See also https://youtrack.jetbrains.com/issue/KT-50227

Shouldn't gradle have access to java.util.Properties and the kotlin stdlib automatically? I have the JVM in Intellij's settings set to java 11...

This sort of sounds like the Gradle Java test fixtures feature. Is that roughly the sort of end result that you’re trying to achieve?

Sadly I don’t think so, I have ArchUnit tests that needs to be run on all my modules. But duplicating those tests on each module is way too much duplication on this project (too many modules)

So could you move the tests into a new separate module? E.g. moduleA moduleATest (depends on moduleA) moduleB (also depends on moduleATest)

Its a bit gross, but it might work ¯\_(ツ)_/¯

I hacked something together last Friday which does what you want: Declare ArchUnit tests in one place and allow you to run them somewhere else: https://github.com/gradle/gradle/commit/0789fa1bfe513d2536b5aaf3cca736f3c20c94f7 The basic idea is to get the classes variant of the project which declares the tests and add them to the arch unit test task in the current project. Note that Gradle needs the classes, not the JAR to actually run the test. Also note that the changes are mostly a spike and still need some more love.

Just released a first dev-preview of gradle-kotlin-delegates@0.0.1 - a utility library for gradle plugin authors, making use of kotlin delegates to make configuration UX lazy yet convenient for the end-users. Additionally it provides delegates chaining support as well as some unique delegates for gradle/system/env properties. Give it a go! Attached is a sneak peak from the readme. Slack Conversation