Hello, I am trying to add to my buildSrc file the dependency for

org.gradle.kotlin.dsl

but I can't find it.

Really wish these gradle plugins had better docs describing what each is really doing under the hood, the sequence of events, and all the configuration options, which there should probably be more of.

Maybe try

./gradlew buildEnvironment

?

Is there

kotllin-dsl

version compatible with kotlin plugin

1.4-M1

?

Hi, I’d like to create a Gradle Task for my Spring Boot App that allows me to start it with a property set:

tasks.register("bootRunDev") {
  System.setProperty("spring.profiles.active", "dev")
  finalizedBy(tasks.bootRun)
}

However, this is not working - the property is not recognized. I also tried to extend the

BootRun

Profile:

task<BootRun>("bootRunDev") {
  systemProperties["spring.profiles.active"] = "dev"
  dependsOn("bootRun")
}

Both approaches don’t work. Is there a way to do it?

What are the different ways to handle version numbers? For now I'm defining a variable twice, in my root of build.gradle.kts and in plugins

Is there any other way? I've seen ways with people making a buildSrc and a kotlin file that has the versions

Hello everyone. What is the equivalent of this groovy snippet in

.kts

?

task all(type: GradleBuild) { tasks = ["independentTask1", "independentTask2"] }

so I have a Kotlin project using Gradle 6.2 with the Kotlin DSL. I want to add a second sourceset main2 and than use the

internal

modifier to mutually hide classes inbetween main and main2. So this is the expected folder structure:

src/main/kotlin
src/main2/kotlin
src/test/kotlin

I've come pretty far by add this to my build.gradle.kts

sourceSets {
    val mainSourceSet: SourceSet = sourceSets["main"]
    val testSourceSet: SourceSet = sourceSets["test"]

    val main2SourceSet: SourceSet = create("main2") {
        compileClasspath += mainSourceSet.output
        runtimeClasspath += mainSourceSet.output
    }

    mainSourceSet.compileClasspath += main2SourceSet.output
    mainSourceSet.runtimeClasspath += main2SourceSet.output
    testSourceSet.compileClasspath += main2SourceSet.output
    testSourceSet.runtimeClasspath += main2SourceSet.output
}

now • code in main can see all the public classes from main2 but not the internal ones • code in main2 can see all the public classes from main but not the internal ones • code in test can see all the public and internal classes from main • code in test can only see the public classes from main2 How do I make the internal classes from main2 accessible to test?

How can I do this notation but in

buildSrc

instead?

implementation(group = "", name = "facebook-login-6.3.0-jetified", ext = "aar")

In buildSrc I can't access the

implementation

function, and I can only do

add("implementation", "put-the-local-aar-here")

, the question is how can I include the local aar through the add function which is only available under only the

buildSrc

?

I am trying to publish my first library to MavenCentral, but i have trouble figuring out how to do it. I followed this guide: https://central.sonatype.org/pages/ossrh-guide.html to create whatever this is: https://issues.sonatype.org/browse/OSSRH-56105 then i tried to configure Gradle with these instructions: https://central.sonatype.org/pages/gradle.html which turn out to be outdated according to this documentation: https://docs.gradle.org/current/userguide/publishing_setup.html so i'm trying to follow that instead, but this documentation isn't very helpful. It suggests using the

publishing {}

block which isn't even possible (workaround here: https://stackoverflow.com/questions/54654376/why-is-publishing-function-not-being-found-in-my-custom-gradle-kts-file-within ) and doesn't give me any information on how to configure it for a kotlin project. can someone help me? maybe someone has a working project setup that i can look at ? I am completely lost

hello! whats the proper way to combine custom

maven-publish

pom.xml

and the one that is generated by

java-gradle-plugin

?, e.g. I got multi module project where I create

pom.xml

for all subprojects so it includes same license info, etc (https://github.com/dariuszkuc/graphql-kotlin/blob/plugin/build.gradle.kts#L132). It looks like

java-gradle-plugin

creates its own (very limited one) and ignores the generated pom (https://github.com/dariuszkuc/graphql-kotlin/blob/plugin/plugins/graphql-kotlin-gradle-plugin/build.gradle.kts#L11). Any suggestions? Thanks!

A noob question: I just added new dependency in

build.gradle.kts

after the prior build, like

dependencies {
    // ...
    implementation("org.springframework.boot:spring-boot-starter-security")
    implementation("org.springframework.security:spring-security-test")
}

, but when I build in IntelliJ, the new dependencies doesn’t get installed: I can’t see them in the External Libraries, and I can’t import them. Am I missing something here? Or is there a certain other way to update the dependencies?

Hey ya. In one of my current projects someone decided to use terraform and docker-compose via Gradle. I am currently struggling with a dependency. I have a task defined like that:

tasks {

    val waitServer by creating {
        group = "Docker"
        description = "Spin-up fresh builds via Docker"
        dependsOn (":reconciliation:dockerBuildImage")
        dependsOn(composeUp)
    }
}

So I would expect that

./gradlew waitServer

would call

dockerBuildImage

on the

reconciliation

module first and then run

composeUp

. But it goes straight into

composeUp

which fails because the docker image from the

reconciliation

module isn’t built yet. Any ideas?

Hi all! Maybe this is impossible, but I wanted to ask: Is it possible to share code between

buildSrc/build.gradle.kts

file and the rest of buildSrc files? I have some configuration that I use in some of my plugins that I also would like to reuse in the build.gradle file. However, this file is used to build the buildSrc, so I cannot reference to any of my buildSrc helper classes. I don’t know if I’m missing something or this just is not achievable. Any help?

[solved] hello! I'm writing custom gradle plugin and trying to figure out proper configuration for tasks and plugin extension • I have 2 tasks (

A

and

B

) that can be executed independently of each other • task

B

can optionally take an input from task

A

output (or just read file from a file system) • [works] I would like to provide an option for end users to either configure tasks directly in their build scripts

// build.gradle.kts
val a by tasks.getting(TaskA::class) {
  propA.set("whatever")
}
tasks.withType(TaskB::class) {
  propB.set("xyz")
  input.set(a.output)
  dependsOn("taskA")
}

• [doesn't work] I would also like to provide an option to to automatically create those tasks and their dependencies if project extension is configured, e.g.

// build.gradle.kts
myExtension {
  propA = "whatever"
  propB = "xyz"
}

Is that even possible?

Hi guys, I’m publishing a multi-platform library (mainly JVM, browser and nodejs), but I also want several artifacts (flavors) per platform, because I want users to be able to pick different modules to avoid unnecessary 3rd party deps. My current approach is having multiple subprojects, some of which are pure JS, some pure JVM, and some multiplatform, with inter-dependencies, but it’s a bit of a hassle. I wonder if there is a better way using many Gradle source sets instead. Maybe just declaring several times the same target with different names for different “flavors” and different sets of deps, but I can’t find any example online, any pointers? If you need more details, here’s my project: https://github.com/joffrey-bion/krossbow

then why do I still see it, if the lib includes the gson via

implementation

anyways?

The code completion has been almost inexistent for me lately i was blaming the 1.4-M1 plugin for that

Hello, I'm very new to Gradle. I adapted an existing Maven project via

gradle init

. It seems to work — it downloads dependencies, builds etc. Now I'm trying to navigate around in the source and it doesn't seem to work with this project. It used to run previously (in other projects), but this is the first time I'm starting a project with Gradle. I just updated IntelliJ too, I hope this isn't some very recent bug. Basically I can't navigate to Gradle-downloaded definitions. Anyone have any ideas? I did invalidate the cache and restart.

I am trying to publish a multiplatform library to bintray with only

maven-publish

plugin but for some reason, there are multiple versions uploaded.

because

DiagnosticControllerTest

doesn't have 151 lines

i recently removed some classpath dependencies from my buildscript section, maybe that's the issue?

hello, im bit stuck on how to define "aar" or "zip" dependency with dependencies constraints (using github/android/plaid -like structure) with

dependencies { constraints { api("${Libs.LIBRARY}:${version}@aar") } }

and using

implementation(Libs.LIBRARY)

in my :app gradle this dependency fails to resolve im sure there is some parameter which could be used to define extensions, but i cant seem to figure out how to do it

hi - new to gradle, using the kotlin DSL, i declare a

val

but they don’t appear to be in scope for the

buildscript

block right below, though work fine for

allscripts

or

subprojects

eg:

val artifactVersion: String by project
buildscript {
  version = artifactVersion // unresolved reference
}
allprojects {
  version = artifactVersion // ok 
}

seeing as these constants are dependent on

project

it’s not clear how I can move this to

buildSrc

and make them available everywhere. if i redeclare them with the

buildscript

block it works but that defeats the purpose (i have many of these constants)

I'm struggling with gradle right now and would appreciate some help. I've got a MPP whih I'm trying to add a custom build of kotlinx-io (courtesy of @altavir) to. I can't seem to get it to resolve the dependency from bintray.

repositories {
    jcenter()
    maven { url = uri("<https://dl.bintray.com/mipt-npm/dev>") }
}

kotlin {

    jvm()
    linuxX64("linux")

    sourceSets {

        val commonMain by getting {
            dependencies {
                implementation(kotlin("stdlib-common"))
                implementation("org.jetbrains.kotlinx:kotlinx-io:0.2.0-npm-dev-7")
            }
        }

Hey at all - i got a question as well. When i run my javafx project in intellij there are no problems - when i run it with "./gradlw run" it complains about me setting up the module system wrong i think

javafx.graphics does not "opens javafx.scene" to unnamed modul

. Does anybody spot the problem? https://gist.github.com/deggers/804cb1ffe6853d968ab58683e0f3318f

Hello everyone! I have a multi-project using Kotlin DSL: https://gist.github.com/x80486/52d5b8f1d584f90732e7d1881df423a7 I'm trying to understand why there are some tasks that are being applied still to the root project. There is nothing there, no

src

, etc. ...so I'm not expecting that Gradle executes anything on it, but on the modules within that umbrella project...any clues? In Maven that's correctly executed, so I think there should be an equivalent in Gradle...thanks in advance!

Hello, World! I'm migrating to

kts

. Let's say I want some globally accessible map for dependency versions (for instance

"gradle" to "6.3", "kotlin" to "1.3.70"

and so on) - and I'd like to be able to access it from the root's build.gradle.kts, and also the other module's. What's the simplest way to do this? Currently I have a solution using

extra

but is there a way to simply add my own

object

to the classpath or something like that?

Is there any way to pass

signing.gnupg.passphrase

as

gradle publish

task param instead of defining it in gradle.properties?