Does the

kotlin("jvm")

plugin automatically apply the

java-library

plugin? I'm sure I remember reading that somewhere but I can't find a reference for it. I'm trying to debug an issue where I'm getting intermittent (!) "unresolved reference" errors when pulling in another module as an

api

dependency 😢 (both modules are libraries, consumed by a third separate module)

We’ve been getting this message in our builds recently and can’t figure out why:

To honour the JVM settings for this build a single-use Daemon process will be forked.

We’ve set up these environment variables:

JAVA_OPTS: '-Xmx3g -Xms1g'
GRADLE_OPTS: '-Dorg.gradle.jvmargs="-Xmx3g -Xms1g" -Dorg.gradle.daemon=false -Dkotlin.compiler.execution.strategy="in-process"'

Are we missing any options? Is there a way to get Gradle to give us more detailed error messages on exactly which settings are different? We’re using

./gradlew

to start up the process, and noticed that it specifies defaults in

DEFAULT_JVM_OPTS

. Are those possibly getting in the way?

I'm getting an error running a task defined in my gradle plugin:

Execution failed for task ':setupMetadata'.
> Extension of type 'KPyExtension' does not exist. Currently registered extension types: [ExtraPropertiesExtension]

but in my plugin I have

// fun Project.setupExtensions(), called first
extensions.create<KPyExtension>("kpy")  // register extension

// fun Project.setupTasks(), called later
task<Task>("setupMetadata") {
    actions.add {
        val target = kotlinExtension.targets.first { it is KotlinNativeTarget } as KotlinNativeTarget
        val ext = the<KPyExtension>()  // error here I'm assuming
        // task action
    }
}

I am able to use the

kpy

keyword in my build.gradle.kts file to configure it and in other parts of the plugin it works fine

Hello, I’m publishing a library which has both java and kotlin code and I’m including

sourceSets.main.allJava

in the sources jar. When I use

Go to definition

in any of the java code it works but on the kotlin it doesn’t, any ideia why? My publish gradle script looks like this

apply plugin: 'maven-publish'

task sourcesJar(type: Jar) {
    from sourceSets.main.allJava
    classifier 'sources'
}

publishing {
    repositories {
        maven {
            name 'myRepo'
            url '<url>'
            credentials {
                username 'user'
                password 'password'
            }
        }
    }
    publications {
        mavenJava(MavenPublication) {
            from components.java
            artifact sourcesJar
        }
    }
}

Hi all! I want to create convention plugins in separate folder. All is going ok except ‘android’ extension doesn’t appear until if I copy internal kotlin extension

After migrating my

kotlin-dsl

Script Plugin out of a

gradle.kts

file into a normal

.kt

file, I am saving ~55 seconds in the configuration phase under "Building included plugins." NOTE: This is using the "Multiplatform Plugin" (see below post, but with JVM Only it still saves ~15 seconds) Code & Gradle Build Scan Links: https://github.com/handstandsam/ShoppingApp/pull/58

If I have a multiproject build and I want to create a new task that runs "build" (as if I ran it from the command line, ie it runs build for all subprojects in the appropriate order) before it does anything else, how can I achieve this? My assumption was that:

tasks.create("whatever") { dependsOn(tasks.build) }

would do the trick however it just runs build on the root project.

has the way to build a shadowJar changed since gradle 7.4 ? I'm running

gradle shadowJar

, but only getting a jar with a Manifest in it in my root

build.gradle.kts

, I have the shadow plugin

plugins {

   ...
   val shadowVersion = "7.1.2"

   kotlin("multiplatform").version(kotlinVersion).apply(false)
   kotlin("plugin.serialization").version(kotlinVersion).apply(false)
   id("com.github.johnrengelman.shadow").version(shadowVersion).apply(false)
}

and then in my module

plugins {
   application
   kotlin("plugin.serialization")
   kotlin("multiplatform")
   id("com.github.johnrengelman.shadow")
}

application {
	mainClass.set("com.blah.MyServer")
}

when running

gradle shadowJar

, I get a fatjar which only contains a manifest, nothing else, not even a class file, but when hitting run in IntelliJ, it runs perfectly fine. my jvm files are under

module/src/jvmMain/kotlin/com/blah/*.kt

what is the alternative to build fat jars? I've tried the zipping approach, but it too is doing the same

tasks.named<Jar>("jar") {
   archiveFileName.set("foo.jar")
   manifest {
      attributes("Main-Class" to "com.blah.MyServer")
   }

   from(sourceSets.main.get().output)

   dependsOn(configurations.runtimeClasspath)
   from ({
      configurations.runtimeClasspath.get().map { if (it.isDirectory) it else zipTree(it) }
   })
}

I am trying to work with TapAndPay private SDK and going by the documentation. I have added this:

allprojects {
    repositories {
        google()
        mavenCentral()
        jcenter()
        maven { url "file:/users/ziv.kesten" } // Local path to the folder into which you unzipped the SDK
    }
}

To my project gradle file, Anf that:

dependencies {
    implementation 'com.google.android.gms:play-services-tapandpay:17.1.2'
}

To my grade.bulld But i fail due to

Unable to resolve dependency for ':lemonade@staging/compileClasspath': Could not resolve com.google.android.gms:play-services-tapandpay:17.1.2.

Anyone knows what am i doing wrong?

hey quick question , lets say im bulding a gradle plugin , and i want it to apply a plugin with a version .For instance

id("com.google.devtools.ksp") version "1.6.10-1.0.2"

Hey guys, Can somone help me on publishing library on maven repository. I am new in publish library. Actually my goal is to publish artifact in private repository. But first I want to start from basic. I have knowledge to store

mavelLocal

. I want to learn more. Thanks

Which should I use with Kotlin 1.7 to replace

targetCompatibility

and

sourceCompatibility

?

Hey guys, I created a library in multiplatform in intellij. In my

settings.gradle.kts

pluginManagement {
     repositories {
         google()
         gradlePluginPortal()
         mavenCentral()
     }
     resolutionStrategy {
         eachPlugin {
             if (requested.id.namespace == "com.android") {
                 useModule("com.android.tools.build:gradle:4.1.2"). // How to update to latest version and what is the use of 4.1.2?
             }
         }
     }
 }
 rootProject.name = "xyz"

I commented in my code. Can someone guide

how can I update my gradle version to latest and what is the use of 4.1.2

that piece of code? I tried to remove 4.1.2 below piece of code then I am getting issue

resolutionStrategy {
     eachPlugin {
         if (requested.id.namespace == "com.android") {
             useModule("com.android.tools.build:gradle:4.1.2")
         }
     }
 }

Error

Build file '/Users/vmodi/IdeaProjects/abc/build.gradle.kts' line: 1

Plugin [id: 'com.android.application'] was not found in any of the following sources:

Hey guys what latest android gradle version supported in intelli idea?

Hey, what is the difference between

id("com.android.application")

and

id("com.android.library")

in plugin ? I got this developer doc. I am new in learning gradle stuff. Thanks

Hey how to convert groovy code in kotlin gradle. I added my kotlin gradle in thread. I want to read github.properties file in my root project

def githubPropertiesFile = rootProject.file("github.properties"); 
 def githubProperties = new Properties() 
 githubProperties.load(new FileInputStream(githubPropertiesFile))

Hey, anybody from Gradle here? Got a question about Gradle Enterprise. Or maybe other people could help 🤷 If I wanted to tag a build failure in order to aggregate build scans using a given tag, is that something I could do from Kotlin code somehow, after catching the exception? Or tagging can only be done via gradle config file using the gradle enterprise plugin?

what do I need to do to get gradle to use more than 4 workers? I tried

--max-workers=12

but it did not change

When trying to use the Kotlin Gradle plugin

1.7.0-RC

in a buildSrc project, the

kotlin-dsl

plugin cannot be applied. Is there any way I can already use

1.7.0-RC

- or is it just not possible yet? The exception is:

Caused by: java.lang.NoSuchFieldError: Companion
	at org.jetbrains.kotlin.gradle.dsl.ToolchainSupport$Companion.createToolchain$kotlin_gradle_plugin(ToolchainDsl.kt:33)
	at org.jetbrains.kotlin.gradle.dsl.KotlinTopLevelExtension.<init>(KotlinProjectExtension.kt:66)
	at org.jetbrains.kotlin.gradle.dsl.KotlinProjectExtension.<init>(KotlinProjectExtension.kt:106)

I've externalized some strings (that I used for classpath versions) to a kts file, but they stopped being recognized after the upgrade, and I have no clue why. Any suggestions or resources?

hi folks, i’m trying to wrap my head around the order of gradle scripts in a multi-project build with a buildSrc for convention plugins. I’ve placed printlns across my *.gradle.kts files so I have a sense of the order from that: 1. ./settings.gradle.kts 2. ./buildSrc/settings.gradle.kts 3. ./buildSrc/build.gradle.kts 4. /build.gradle.kts 5. buildSrc convention plugins 6. project build.gradle.kts From that I see that I cannot define say the kotlin jvm plugin version in /build.gradle.kts if it is also defined in buildSrc/build.gradle.kts because gradle seems to only want the version declared once and as early as possible. So my question is, where can i find more information on this ordering and details about when/where versions can be defined?

Has anyone been successful in using the new Android Gradle plugin's UI test sharding feature across managed virtual devices? I've got it to the point where Gradle launches four emulators; but then produces a test report saying they all either 'timed out' or failed to install the APK 💔. Traces in 🧵 👉

Hello, can someone tell me more about

buildSrc

. Is

buildSrc

a 1-to1 replacement to

subProjects

and which one do you recommend to start a new multi module project if you're not writing a gradle plugin. I personally started using

subProjects

+

gradle.properties.kt

to share dep versions and found it to be super easy to use and flexible. Imagine a project where we share dependencies, you might have a root build.gradle, then 2 parents modules, then multiple sub module in each parent. Using subProjects we can have one in Parent A build.gradle.kts so that it doesn't impact sub modules of Parent B etc. From my understanding

buildSrc

is more for if you want to write a gradle plugin with logic and want to re-use kotlin kts script then you'd use the buildSrc and define kotlin files there instead of including scripts

include("myScript.kts")

. Or if you have complex gradle build logic then you'd use buildSrc as a place to essentially write that build logic. is that correct? Thanks

Is it possible to load local aar files with the gradle version catalog?

Hello, I am discovering the new

plugins

declaration. Applying below in the root Gradle file

plugins {
    id("com.android.application") version "7.2" apply false
    id("com.android.library") version "7.2" apply false
}

But I also need to apply

Gradle

plugin in

buildSrc

so I have this in there

implementation("com.android.tools.build:gradle:7.2.0")

but then IDE throws an exception

Error resolving plugin [id: ‘com.android.application’, version: ‘7.2.0’, apply: false]

> The request for this plugin could not be satisfied because the plugin is already on the classpath with an unknown version, so compatibility cannot be checked.

How do I have the same plugin works for the both places?

Have you ever seen this error message?

Could not initialize class org.jetbrains.kotlin.gradle.targets.js.ir.KotlinJsIrTargetPreset$WhenMappings

I try to upgrade my fairly complex multiplatform project to Kotlin 1.6.21 (and Compose/MP 1.2.0 alpha 😡) but my hair falls out, I always get different errors and failures 😞

Can I get some help on how to properly use the

distribution

plugin? I have a service which has a part which generates some kotlin code from a yaml file (using

snakeyaml

). But that’s only used manually by developers and isn’t required runtime. Yet, their dependencies defined

compileOnly

still appear in

build/install/service/lib

folder. I’ve tried to exlcude them by

application { 
   applicationdistribution.exclude("snakeyaml*.jar)
}

but that kept the jar in the lib folder. I wonder what’s the right way to isolate these sub-distributions and include only the required dependencies.

I'm trying to implement Gradle Version Catalogs on my project but I got this error!!

I often run into the following error in Idea when I try to build a project (CTRL+F9):

...
> Task :buildSrc:build UP-TO-DATE

...

FAILURE: Build failed with an exception.

* What went wrong:
Task 'assemble' not found in root project 'xxx'.

...

(See comment for stacktrace.) Build works if I execute Tasks/build/build in the Gradle tool window. Maybe is there a ticket to track this issue? Environment: Idea CE 2022.1.2, Kotlin 1.6.21, Gradle 7.4.2