Hi all. I am trying to create a custom task that check dependency graph, verify that some dependency are present and fail build if they are. I have a

dependency

task that prints all the dependencies, but I am not able to assemble that pieces to a working solution.

tasks.register("checkForAndroidxDependencies") {
    description = "verify that no androidx dependencies are present"
    group = "verification"

    dependsOn("androidDependencies") // how do I get the output of the androidDependencies?
   
    doLast {
        exec {
            commandLine = listOf("grep", "androidDependencies") // Are there any way to execute the "grep" on the androidDependencies?
        }
    }
}

Any help will be much appreciated.

Hello again Kotlin Kommunity. I would like to know if there’s a smart way to read

gradle.properties

files between modules. For example if I have

project/
    module1/
        gradle.properties
    module2/
        gradle.properties
...etc

and in

module2

i want to be able to pull a property from

module1

like say

appVersion

is there a way to do this? or is that just a bad idea?

Good morning, Gradle Masters. Any ideas why during project build gradle does not throw/fail with an Exception? I am getting the

should throw

printed in build logs, but for some reason it is BUILD SUCCESSFUL

project.configurations.all {
    resolutionStrategy.eachDependency {
        if (this.requested.name.contains("abc")) {
            println("should throw")
            throw IllegalArgumentException("Can not use abc dependency ")
        }
    }
}

FYI: If you are using Gradle 7.0-7.1, configure Kotlin daemon options via

org.gradle.jvmargs=-Dkotlin.daemon.jvm.options=...

plus using Kotlin DSL - it may happen spawned Kotlin daemon will ignore them. This is happening when Kotlin DSL scripts are compiling and this workaround is set by Gradle. Either update Gradle version or use

kotlin.daemon.jvmargs

property.

What could be the reason for this huge white gap between the configuration and the execution phase?

I have two multi-platform builds -- neither of which have a

compileClasspath

configuration or

main

source set. However, if I include the second build in the first build, now I get a

compileClasspath

configuration coming from a

main

source set (and this breaks the jetbrains compose runtime dependency). Any ideas on where to look?

TBH maybe this is not related to Gradle but not sure where I should post this one. I have a custom theme in an isolated module for compose based on the library material, thanks to Gradle I can just use

implementation

instead of

api

to avoid exposing Material, but it is becoming inviable the amount of dupe code of things are not going to change in the foreseeable future (animations for example). So I moved my components to be a mix of my custom theme params plus material params. Problem is I don't want expose some composables/imports from Material lib, so they can't be imported and not only fix the issue of IDE suggesting them, even just failing in compile time too. Is it possible to be done with Gradle easily?

is there an advantage to publishing gradle plugins to the gradle plugin portal or is sonatype/central fine?

Dumb question --- what’s the correct way to make a custom task that doesn’t take parameters? It seems like if I don’t specify any @Inputs, gradle complains that the constructor should be annotated with @Inject. If I annotate the task constructor with @Inject, gradle complains that the constructor doesn’t take any parameters.

Is there anything I can do to improve configuration time? I already went through unnecessary plugins and dependencies, yet its like 15seconds Anything other than "not have so many modules"?

anyone know how to fix:

Reason: Task ':generateMetadataFileForPluginMavenPublication' uses this output of task ':publishPluginJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

?

what is this gap? is it possibly gc or something? because the one bar going thourgh the gap, is for sure not something others are awaiting for (its 3 apps being built, so app module of appA for sure is not a dependency to appB etc)

this is a pretty simple task that i’m having trouble finding an answer for, but is there a way to set an environment variable for all tasks from the gradle build file? it looks like the `JavaExec`type task allows for it by providing a

setEnvironment

method, however i want it to be available for all of my

jsBrowser..

type tasks. so in summary i want to: 1. get a value from the properties file ✅ — this is easy 2. set that as an env variable from the gradle.build.kts file so that its available to all tasks any help will be greatly appreciated!

Hey I noticed every android gradle module has debug & release variants. I think it would help config times if I were to disable the release variant, as its never necessary in our case in local development How would I do that?

Is there a nice way to have 2 distinct sets of instrument tests on android (I assumed it would be the same for plain unit tests)? E.g. I have my normal set of Tests

A

. But sometimes I want to run a defined set of Tests

B

but not run the Tests from

A

. I tried utilizing

@LargeTest

etc and Test suites, but it didn't seem to work out nicely 💭 I'd love to not touch Tests

A

in any way. Note: All tests are within one gradle module

I've migrated groovy to kotlin dsl, I am able to build an app, but I am unable to get rid of the warnings in AS. Anyone encountered it?

Is it an unexpected use case to write extension-functions for a plugin's classes in

buildSrc

? I'm hitting unexpected trouble quite early on 🧵 👉

Hey guys! I'm using some Kotlin features in my

build.gradle.kts

that are experimental and require a

RequiresOptIn

annotation like

@ExperimentalPathApi

. I'm using those in the build script with the

@OptIn

annotation. Problem/Issue now is a warning in the build script that I did not add the

RequiresOptIn

to the kotlin compiler options - but where do I add this compiler option for the Gradle script Kotlin compiler? An example of the issue can be seen here: https://github.com/chrimaeon/curriculumvitae/blob/03663b8ee32f3f83746536f7ac093df5a93a5953/app/build.gradle.kts#L40

Is there a specific reason to use Gradle properties for things like

kotlin.mpp.stability.nowarn

,

kotlin.native.binary.memoryModel

or

kotlin.stdlib.default.dependency

? I'd love these to be moved to setters/getters APIs in the "kotlin" extension instead: 1. that'd allow proper API lifecycle management (preview, stable, deprecated) and avoid cluttering the

gradle.properties

file with properties that are not supported any more 2. that can be more precise about when the property is needed. I understand something like

kotlin.native.binary.memoryModel

is only for binaries so adding it only in

binaries {}

makes this explicit compared to a global

gradle.properties

prop 3. Maybe it'll play better with Gradle configuration cache?

I have a Gradle project with a lot of Kotlin sub-mobules. I'd like to configure

kotlinOptions

and

kapt

for each of those modules without repeating myself, how can I centralize configuration ? I've found very few official resources on Kotlin project modularization.

I posted this on #android, but maybe this is a better place for this question: Is it possible to compile multiple android gradle modules into one aar file using Kotlin DSL, or do I have to publish each one separately? Say I have a

:common

some-android-lib

depends on

:common

and

android-app

depends on

some-android-lib

, I want to only publish

some-android-lib

to maven and include

:common

in it, and then only refer to

some-android-lib

in

android-app

...

Hi, I‘m having an android  project. and I notice it try to find some directory that I had never create when I try to assemble it , and if I got lot of flavors. It looks like spent lot of time to find those directories that never exist. Can I skip those step ? If I skip those step, would it help me to optimize build time ?

Is it possible to get autocompletion for build.gradle files in AS?

In a multi-module project, with Groovy, I can have a base gradle file that is imported into other files, using

apply from: "$rootDir/base_library_module.gradle"

- is there something equivalent with Kotlin DSL for

build.gradle.kts

?

Is there an equivalent to 

maxParallelForks

 for 

KotlinNativeTest

 tasks in Gradle? I'm trying to prevent native macOS tests from running in parallel, but I can't seem to find the correct config. Note that my diagnosis might be wrong, but I'm getting an error that I used to get because of parallelism (my tests access an external resource that doesn't support parallelism). (this used to be posted in #kotlin-native but got no answer in a few days, so I guess this channel might be more appropriate)

does anyone know why this example of convention plugins in the documentation doesn’t work or what’s needed to make it work? https://docs.gradle.org/current/userguide/declaring_dependencies_between_subprojects.html#sec:project_jar_dependencies

Anyone knows how to create gradle JavaExec configuration for multiplatform project?

tasks.create<JavaExec>("run") {
    classpath = //?
    mainClass.set("com.example.MainKt")
}

sourceSets

container is at this point empty.

configurations

container does not have

jvmMainRuntime

configuration.

I'm trying to include output of copy task in jvm resources inside multiplatform project, but they're not effectively present in jar, not avaiable to run task. Is there proper way to do it? Other than modyfing jar and run tasks.

kotlin.jvm().compilations["main"].defaultSourceSet.resources.compiledBy(someCopyTask){
    val directoryProperty = project.objects.directoryProperty()
    directoryProperty.set(someCopyTaskOutputDir)
    directoryProperty
}

Hi, I am trying to publish a module named 

core_ds_component

 of an Android project to artifactory. When I run the publish command, I get this error. I couldn’t find dokka in the dependency graph of this module. Does anyone has any idea what could be wrong?