set the channel description: Any discussions about the recent releases and the features there. This is an addition to the #CJWG8VDM0 channel which we use for announcements

@Vladislav Chesnokov You will see the reason for this channel soon, I hope 😛

set the channel topic: Gradle Build Tool 8.7 Release 🚀 Overview: https://gradle-community.slack.com/archives/CJWG8VDM0/p1712921270824479

<!channel> The Gradle Build Tool 8.7 release stream is live:

We're experimenting with new formats, so any feedback is welcome!

👏 et 🙇 to @Jendrik Johannes for becoming the first ever non-Gradle Inc. presenter in the release video. We will be doing it more, and hopefully not just for the Gradle Build Tool core :)

And one of my next video goals is to ensure these videos go live within one week after the release is published

Speaking of the public roadmap, there are some changes there: https://github.com/orgs/gradle/projects/31 It is still WiP, but you can see there are now time horizons instead of quarters. The aspirational release milestones and quarters are now available in extra tabs

So, any comments about the features & Co in 8.7?

in Gradle 8.8 release notes - I suppose following is a typo and should be "Since Gradle 8.8 ..."

Since Gradle 8.7, it's been possible for plugins to define their own dependencies-like block.

In the 8.8 release notes at "New Gradle lifecycle callbacks" links to https://docs.gradle.org/8.8-rc-1/javadoc/org/gradle/api/IsolatedAction.html which says > This approach ensures that sharing mutable state across targets via any means (including BuildService, which are not supported) is prevented. > But then the example shows how to use shared mutable state across two actions. What do I get wrong there?

was there a change in behavior for

-m

flag? I noticed that its not passed down to included builds

Hey, Gradle team! When do you plan to bring Kotlin 2.0+ to Gradle?

Looks like

LifecycleAwareProject

info is missing in 8.10-RC-1 release notes

small mistake in the 8.10-RC1 release notes. https://github.com/gradle/gradle/issues/10867 is included, but it was actually closed as a duplicate.

A typo in the migration guide from Gradle 8.9 to 8.10: > Deprecated extending configurations in the same project It should be rephrased as it’s about deprecation of extending configurations from different projects

Could I post a feature request here? Or discuss it?

Hey @Suresh, Replying here to your report / question How is Gradle made aware of that added JDK with native image capability on Windows?

Seeing an issue with 9.0-rc3 that I don't see with 8.14.3:

❯ gradle tasks

FAILURE: Build failed with an exception.

* Where:
Build file '/my-project/build.gradle' line: 31

* What went wrong:
A problem occurred evaluating root project 'my-project'.
> Could not resolve all artifacts for configuration ':detachedConfiguration3'.
   > Cannot resolve external dependency org.springframework.boot:spring-boot-dependencies:3.5.0 because no repositories are defined.
     Required by:
         root project 'my-project'

For context, here is the beginning of the project build file... note there are repositories defined.:

───────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: build.gradle
───────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ plugins {
   2   │     id 'java'
   3   │     id 'maven-publish'
   4   │     id 'jacoco'
   5   │     alias(libs.plugins.cyclonedx)
   6   │     alias(libs.plugins.openapi.generator)
   7   │     alias(libs.plugins.shadow)
   8   │     alias(libs.plugins.spotless)
   9   │     alias(libs.plugins.spring.dependency.management)
  10   │     alias(libs.plugins.spring)
  11   │ }
  12   │ 
  13   │ group = 'my.company'
  14   │ 
  15   │ // disable building jar that contains only bytecode of your source code (slim jar)
  16   │ // shadowJar will build jar that not only contains bytecode of your source code but also JARs from third parties
  17   │ // We will be publishing only the shadow jar (fat jar) into maven repo and disabling the slim jar will help reduce cost and speed up build time.
  18   │ jar.enabled = false
  19   │ bootJar.enabled = false
  20   │ 
  21   │ // Required by task ':shadowJar' when the archive contains more than 65535 entries.
  22   │ // Beta versions of "stripe-java" bring the archive over the limit.
  23   │ tasks.withType(Zip) {
  24   │      zip64 = true
  25   │ }
  26   │ 
  27   │ configurations {
  28   │     compileOnly {
  29   │         extendsFrom annotationProcessor
  30   │     }
  31   │     all*.exclude module : 'spring-boot-starter-logging'
  32   │ }
  33   │ 
  34   │ repositories {
  35   │     mavenCentral()
  36   │     mavenLocal()
  37   │     maven {
  38   │         name = 'GitHubPackages'
  39   │         url = uri('<https://maven.pkg.github.com/my-company/my-other-project-0>')
  40   │         // the "githubUser" and "githubToken" properties should be set
  41   │         // by each developer individually under ~/.gradle/gradle.properties, e.g.:
  42   │         // githubUser=my-github-username
  43   │         // githubToken=42ed8...99a7c
  44   │         credentials {
  45   │             username = githubUser
  46   │             password = githubToken
  47   │         }
  48   │     }
  49   │     maven {
  50   │         name = 'GitHubPackages'
  51   │         url = uri('<https://maven.pkg.github.com/my-company/my-other-project-1>')
  52   │         credentials {
  53   │             username = githubUser
  54   │             password = githubToken
  55   │         }
  56   │     }
  57   │     maven {
  58   │         name = 'GitHubPackages'
  59   │         url = uri('<https://maven.pkg.github.com/my-company/my-other-project-2>')
  60   │         credentials {
  61   │             username = githubUser
  62   │             password = githubToken
  63   │         }
  64   │     }
  65   │ }
  66   │ 
  67   │ java {
  68   │     toolchain { languageVersion = JavaLanguageVersion.of(21) }
  69   │ }
... snipped the rest  ...

Changing the

build.gradle

file so the repositories are defined before the configurations fixes the issue, but this was not required with Gradle 8.14.3

Cheers to the latest release of Gradle 9.2.0 supporting a very nice version of Java's class file. That being said, is there any performance benefit to be had from using the Daemon JVM toolchains feature to set it as the same version as the project's language level? I've mostly been using JAVA_HOME to run Gradle the entire time (even in IDE). Though, IntelliJ is thankfully smart enough to de-bump the JDK version on older versions of Gradle, and I can use SDKMAN to swap the JDK for the current shell if I'm invoking Gradle through the terminal.