https://gradle.com/ logo
Join Slack
Powered by
# community-support
  • m
    Is there a way to run a gradle task always when all the tasks finish? (to clean up) I'm thinking android studio but this is most probably generic question for gradle. If not, I'll ask in android channel.
    m
    a
    • 3
    • 15
  • c
    Are there any "popular" or big name library authors that self host their artifacts? (basically. not on maven central?) I'm trying to possibly self host (for reasons) and trying to see what the "industry standard" is in terms of hosting the artifacts, but also how the documentation states the inclusion of the artifact repository.
    e
    j
    +3
    • 6
    • 22
  • a
    Do the checksums in the Gradle Module Metadata file get used for anything? I read this issue, which I think implies Gradle doesn't use them at all.
    👀 2
    l
    • 2
    • 2
  • c
    What steps does maven take to search for artifact files. For example, it seems like it searches for a module file, then pom, then jar or aar? My quesiton stems from the fact that I've noticed that a lot of 3rd party artifact repository don't present you with an html tree to browse, so it looks like it's a guess and check sort of system.
    👀 2
    e
    • 2
    • 3
  • н
    Is there any difference between kt or kts file format for convention plugins in includeBuild project?
    👀 1
    m
    l
    • 3
    • 7
  • j
    Hello 👋 Which is the way to get all dependencies, direct and transitive ones in a module? I tried with no luck by getting the 
    implementation
    configuration and looking for the dependencies there.
    m
    v
    l
    • 4
    • 86
  • e
    Is there any way to tell Gradle to pin worker threads to only use CPU performance cores (I'm using an i9 12900k)? I'm curious if the faster throughput will offset the lower parallelism enough to make it worth it. I have some tasks that use 100% of all CPU cores, and I sometimes like to do other things while building (which should be fine using the efficiency cores).
    👀 1
    l
    m
    +2
    • 5
    • 11
  • н
    Is there any way inside build.gradle.kts to define some variable that will be accessible right away by plugins applied in 
    plugins {}
    block.
    m
    e
    l
    • 4
    • 18
  • m
    Is it possible to define the mapping from the maven coordinates to project name as part of the 
    includeBuild()
    context? this to keep the mapping from module to project at its origin
    l
    v
    • 3
    • 7
  • c
    I've got an android app module's build.gradle file that is using a modern plugin block with alias' for everything EXCEPT for 
    id("org.jetbrains.kotlin.plugin.parcelize")
    . I converted it to an entry in my toml, and converted it to 
    alias(libs.plugins.kotlin.parcelize)
    in my build file. but now it wont build UNLESS I go to root build.gradle and add ``alias(libs.plugins.kotlin.parcelize) apply false` ` Why is that needed when using version catalog... but when I just used 
    id("org.jetbrains.kotlin.plugin.parcelize")
    it did not need the extra line in my root build.gradle (bonus points: how did it even work with id if I never declared the version of the plugin I wanted until i now had to add it in version catalog declaration)
    e
    e
    • 3
    • 8
  • s
    I am trying to upgrade spring boot from 3.3.13 to 3.5.7. Using gradle Gradle 4.8. Getting this error A problem occurred configuring root project 'test-project. > java.util.concurrent.ExecutionException: org.gradle.api.GradleException: Failed to create Jar file /Users/sachinhr/.gradle/caches/jars-9/b622d58fb9140b4bb070fced1ad683db/spring-core-6.2.12.jar. > Tried deleting gradle cache and rebuilding. Still gives same error
    c
    v
    • 3
    • 2
  • m
    I'm looking to better isolate the Gradle user home in tests. Say I work on a Gradle plugin, and I want to test it with TestKit. I want the test to be reliable in CICD, so I don't want it to be polluted with my real 
    ~/.gradle
    . What I currently do is to populate 
    build/gradle
    with what I need, namely 
    gradle.properties
    , some 
    init.d/
    scripts, and I point TestKit there with 
    withTestKitDir()
    . This is mostly ok, except that the various Gradle distributions are downloaded in such test user home directories. This is annoying because it's slow the first time around, and also because these directories are not getting cleaned up. E.g. in 1 project after playing with only 9.2.0 and 9.2.1, I have almost 2GB of mostly generated Gradle jars and transforms. Is there a way to improve this? So basically, I don't care to isolate the Gradle artifacts and transforms from my primary Gradle user home, but I definitely want my user home properties and init scripts not to be visible in tests. Is there some way to achieve properties/init script isolation while also avoiding cache duplication?
    t
    a
    • 3
    • 4
  • g
    Hi, we have a bunch of composite builds in our repository, and want to set up the gradle cache to make them faster. when we run our PR checks, each project runs the same build cache setup logic. since establishing the environment where we run (is it on CI? is it on desktop? is it in a docker container? which branch is it? etc.. ) can take some time, i am looking into options on how to just do just once, and not run those checks for every project... now it seems that i can calculate what i need, and store it with 
    System.setProperty
    - and if i do, every other project can just check if the property is set, and if it is, use it, and not do the calculations. this actually works, the checks run only once, yay. however this solution feels a bit hacky, as it is kind of circumventing gradle to pass along the information. the question is, are there some alternatives that are better for this use case? we are currently using 
    8.11.1
    - is this solution still going to be viable in later releases?
    a
    • 2
    • 6
  • c
    I am confused about publishing version catalogs. The preliminary example given has. I am kind of assuming that we only need to use the 
    catalog {...]
    for publishing one?
    Copy code
    catalog {
    // declare the aliases, bundles and versions in this block
    versionCatalog {
        library("my-lib", "com.mycompany:mylib:1.2")
    }
}
    but then says we "The catalog must be created programmatically, see Programming catalogs for details." which uses the format
    Copy code
    dependencyResolutionManagement {
    versionCatalogs {
        create("libs") {
            version("groovy", "3.0.5")
            version("checkstyle", "8.37")
            library("groovy-core", "org.codehaus.groovy", "groovy").versionRef("groovy")
            library("groovy-json", "org.codehaus.groovy", "groovy-json").versionRef("groovy")
            library("groovy-nio", "org.codehaus.groovy", "groovy-nio").versionRef("groovy")
            library("commons-lang3", "org.apache.commons", "commons-lang3").version {
                strictly("[3.8, 4.0[")
                prefer("3.9")
            }
        }
    }
}
    p
    • 2
    • 2
  • y
    how to add an new Property field to objects created by other plugin(The class of the object is also provided by other plugin)
  • y
    Copy code
    runs{
    "named"{
        propA= false
    }
}
    🧵 1
  • y
    Like this, I want to add a Property a
    🧵 1
    v
    • 2
    • 1
  • c
    at some point it would seem that doing in 
    libs.versions.toml
    Copy code
    foo = ...
foo-bar = ...
    and then
    Copy code
    dependencies { 
  implementation(libs.foo)
  implementation(libs.foo.bar)
    started working, does anyone know when? because I recall that 
    foo
    wouldn't work because it wasn't the "end provider" so to speak.
    v
    a
    • 3
    • 30
  • m
    I vaguely remember there being a way to assign to a Property<String> with = in kotlin build scripts, but now can't find anything about that and gradle seems to be rejecting it with 
    [ASSIGNMENT_TYPE_MISMATCH] Assignment type mismatch: actual type is 'String', but 'Property<String>' was expected.
    Is prop.set the only way to do this in current gradle versions?
    e
    • 2
    • 6
  • m
    What am I doing wrong in my shared configuration setup? Root project:
    Copy code
    val outputJar by configurations.creating {
    isCanBeConsumed = false
}

dependencies {
    outputJar(project(":mmorpg-mod", outputJar.name))
}

tasks {
    val deploy by registering(SshDeployTask::class) {
        host = prop("sshDeployHost")
        port = prop("sshDeployPort").toInt()
        user = prop("sshDeployUser")
        if (localProps.hasProperty("sshDeployPass")) {
            password = prop("sshDeployPass")
        }
        remoteDir = prop("sshDeployPath")

        from(outputJar)
    }
}
    mmorpg-mod subproject:
    Copy code
    val outputJar by configurations.creating {
    isCanBeResolved = true
    isCanBeConsumed = true
}

artifacts {
    add(outputJar.name, tasks.named("remapJar"))
}
    Error:
    Copy code
    Could not determine the dependencies of task ':deploy'.
> Could not resolve all dependencies for configuration ':outputJar'.
   > Could not resolve project :mmorpg-mod.
     Required by:
         root project 'mmorpg-mod'
      > A dependency was declared on configuration ':mmorpg-mod:outputJar' of 'root project :' but no variant with that configuration name exists.
    t
    • 2
    • 2
  • m
    Hello! I'm interested in attempting to build Gradle from source, without using a binary bootstrap. Are there people in here interested in that, or having experience/knowledge with attempts to do so?
    t
    e
    v
    • 4
    • 15
  • j
    i have a gradle dependency that has been maven relocated to a new group id, and the new group id also provides the old group as a capability. depending on the old group id (and that group id only) gives the following error, even though only one dependency is declared:
    Copy code
    % ./gradlew run
> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve org.lz4:lz4-java:1.8.1.
     Required by:
         root project :
      > Module 'org.lz4:lz4-java' has been rejected:
           Cannot select module with conflict on capability 'org.lz4:lz4-java:1.8.1' also provided by [at.yawk.lz4:lz4-java:1.8.1(apiElements)]
   > Could not resolve at.yawk.lz4:lz4-java:1.8.1.
     Required by:
         root project : > org.lz4:lz4-java:1.8.1
      > Module 'at.yawk.lz4:lz4-java' has been rejected:
           Cannot select module with conflict on capability 'org.lz4:lz4-java:1.8.1' also provided by [org.lz4:lz4-java:1.8.1(compile)]
    poc: https://github.com/yawkat/test-case-gradle-rename-capability is this a bug or is the metadata not supposed to be used this way?
    v
    t
    • 3
    • 31
  • s
    How to exclude files from embed jars? I want to exclude the classes in 
    META-INF/versions/24/
    in the dependency jar embed. I'm embedding it with a custom configuration
    Copy code
    val embedBoot by configurations.register(lowerCamelCaseGradleName(featureName, "embedBoot")) {
    isTransitive = false
    attributes
        .attribute(ArtifactTypeDefinition.ARTIFACT_TYPE_ATTRIBUTE, ArtifactTypeDefinition.JAR_TYPE)
        .attribute(REMAPPED_ATTRIBUTE, false)
        .attribute(INCLUDE_TRANSFORMED_OUTPUT_ATTRIBUTE, true)
        .attribute(IncludeTransformationStateAttribute.ATTRIBUTE, IncludeTransformationStateAttribute.None)
}
project.dependencies {
    embedBoot(catalog.reflect)
    embedBoot(catalog.classTransform)
    embedBoot(catalog.classTransform.additionalClassProvider)
    embedBoot(catalog.bytebuddy.agent)
}
tasks {
    named(generateModsTomlTaskName) {
        enabled = false
    }
    named<Jar>(jarTaskName) {
        from(embedBoot) {
            into("libs/boot")
        }
    }
}
    m
    • 2
    • 10
  • k
    nexus started limiting requests count (https://help.sonatype.com/en/sonatype-nexus-repository-3-87-0-release-notes.html) and in the same time they count incorret credentials requests (https://github.com/sonatype/nexus-public/issues/736), in my case i see that gradle is not failing and sending thousands of requests to private nexus after password change. So how to tell gradle to fail on first wrong credential request? It silently ignore it and continue build. (not just add task that will do HEAD request on each build first and not post dependency resolution).
    l
    t
    v
    • 4
    • 29
  • m
    I have a vague memory from reading gradle docs that convention plugins (defined as 
    .kt
    files in a 
    buildSrc/
    -type location, exposed to consuming builds) are preferred over binary plugins (defined as 
    .gradle
    files in that same consuming build) for performance reasons, but I'm not able to find those references in those docs now - does my memory serve me correctly here?
    t
    v
    • 3
    • 12
  • e
    With project isolation, is it ok to access root project lifecycle tasks from a sub project? e.g. 
    rootProject.tasks.named("check").configure { dependsOn(myTask) }
    m
    p
    t
    • 4
    • 21
  • m
    Is there anyone who can help me in integrating firebase with my flutter project
    c
    • 2
    • 1
  • s
    Is there a sane way to get the version of an (unapplied) settings plugin in a conventional plugin inside 
    buildSrc
    ?
    v
    t
    l
    • 4
    • 9
  • d
    Hi I'm trying to use multiple versions of a package that has an identical classpath. Is there a way to relocate each version of these plugins to custom locations (like org.example -> org.example.v1)? I know there is the shadow plugin but it seems to only support relocating the entirety of that classpath which seems like it would relocate all the versions to the same spot. Is there another way to do this? Thanks!
    m
    v
    • 3
    • 34
  • s
    How can I list dependencies between project in a multi-project, without dependencies on external artifacts? Or actually, what I'm interested in in this case, is to list projects in the order they would be built (i.e. breadth-first start from the leaves in the project dependency graph).
    v
    • 2
    • 2