This message was deleted.

This message was deleted.

How to solve it

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello, I’m working on a composite build project that uses version catalogs (gradle 7.5.1) on one of the leaf nodes (doesn’t include another build) Running into this error

Error resolving plugin [id: 'org.jetbrains.kotlin.jvm', version: '1.7.0']
> 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.

on this block

plugins {
    alias(libs.plugins.kotlin.jvm)
    alias(libs.plugins.detekt)
    id 'java-library'
    alias(libs.plugins.kotlin.kapt)
    id 'maven-publish'
}

I tried using the solution described in this gradle issue, but ran into this other issue

Could not compile build file '<...>/projectA/build.gradle'.
> startup failed:
  build file '<...>/projectA/build.gradle': 2: argument list must be exactly 1 literal String or String with property replacement

This started happening after I applied a custom gradle settings plugin (linked in this thread) Does anyone know why this is running into an issue?

This message was deleted.

Who is dealing with Android Studio, out here?

This message was deleted.

I tweaked a bunch of stuff in my core Gradle logic, and now one of my projects prints a warning for each Kotlin multiplatform target, that the

<target>Klibraries

and

<target>Classpath

configurations were resolved during configuration time. Any ideas on where the best places are in my Gradle logic to start looking for what is causing this?

This message was deleted.

This message was deleted.

Hello everyone, - We are excited to announce our first Developer Productivity Engineering Summit! The event will take place in San Francisco on November 2-3, 2022. In this two-day summit we’ll focus exclusively on Developer Productivity Engineering, featuring speakers from Airbnb, DoorDash, Google, Gradle, LinkedIn, Microsoft, Netflix, Slack, Square, and Uber. Check out the event details at the DPE Summit website << dpesummit.com>>. Use the code gc-slack-100 to receive a $100 discount off the registration price. See you there!

This message was deleted.

Any thoughts on https://discuss.gradle.org/t/is-it-good-practice-to-apply-a-platform-dependency-to-all-configurations/37817? I have a few dependencies in implementation, api, annotationProcessor, compileOnly and test that I'd like to all use the spring platform bom.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello everyone, - just another DPE Summit related announcement it is 🙂 We opened a new channel for updating the community about our event. Go check the #C04063WRPT4 channel --> <https://gradle-community.slack.com/archives/C04063WRPT4 >>

This message was deleted.

This message was deleted.

This message was deleted.

👋 Hello, team! I am working on updating the Grails framework to Apache Groovy 4. I am struggling to solve the following problem:

* What went wrong:
Execution failed for task ':grails-core:compileGroovy'.
> Could not resolve all files for configuration ':grails-core:annotationProcessor'.
   > Could not resolve org.codehaus.groovy:groovy-bom:3.0.10.
     Required by:
         project :grails-core > io.micronaut.spring:micronaut-spring-annotation:4.1.1 > io.micronaut:micronaut-bom:3.5.1
         project :grails-core > io.micronaut.spring:micronaut-spring-annotation:4.1.1 > io.micronaut:micronaut-bom:3.5.1 > io.micronaut.groovy:micronaut-groovy-bom:3.1.0
      > No matching variant of org.apache.groovy:groovy-bom:4.0.4 was found. The consumer was configured to find a runtime of a library, packaged as a jar, and its dependencies declared externally but:
          - Variant 'apiElements' capability org.apache.groovy:groovy-bom:4.0.4:
              - Incompatible because this component declares an API of a platform and the consumer needed a runtime of a library

I think the above is happening due to

annotationProcessor "io.micronaut.spring:micronaut-spring-annotation:$micronautSpringVersion

in the

build.gradle

file. Is there an easy way to exclude the

groovy-bom

from

annnotationProcessor

something as the following:

annotationProcessor("io.micronaut.spring:micronaut-spring-annotation:$micronautSpringVersion") {
        exclude group: "org.codehaus.groovy", module: "groovy-bom"
    }

I would appreciate any help with the same.

This message was deleted.