Gradle 8.9

What's new in this version:

New features and usability improvements:
Error and warning reporting improvements:
- Gradle provides a rich set of error and warning messages to help you understand and resolve problems in your build. This release makes it easier to deal with dependency management issues and configuration cache misses.

Better messages for common dependency variant issues:
- Gradle provides a powerful dependency management engine that is variant-aware. That means every dependency can have multiple variants (for example, for different Java versions) with separate transitive dependencies. This release significantly improves error reporting around dependency variants, continuing to address requests from a highly voted issue.

Variant ambiguity:
- When Gradle attempts to resolve a dependency and finds multiple variants available, all of which define attributes that would satisfy the resolution request, the resolution fails with a variant ambiguity error.

Missing variants:
- If a dependency on a project that declares no variants is requested, dependency resolution will fail. This can happen when depending on a project that does not apply any JVM plugins.
- IDE integration improvements:
- Gradle is integrated into many IDEs using the Tooling API. The following improvements are for IDE integrators.

Better compilation failure reporting for IDEs:
- Gradle now collects and manages problems through the Problems API. This means IDEs and other Tooling API clients can access precise and detailed information about any issues that arise during the build process.
- Several Gradle components leverage this new API, including deprecation, task validation, and the dependency version catalog. In this release, the Java compiler is also integrated into this infrastructure.
- This integration allows popular IDEs like IntelliJ IDEA and Visual Studio Code to provide a seamless and accurate visual representation of Java compilation issues, eliminating the need to parse text output from the compiler. Eclipse Buildship will include this in its upcoming release.

Other improvements:
Daemon JVM information report:
- Before this release, running gradle --version displayed the JVM used to launch Gradle, but this JVM did not execute any build logic. Instead, Gradle started a Daemon that actually ran the build. Then, Gradle 8.8 introduced a feature that allowed users to configure the JVM used to run the Gradle Daemon.
- In this release, users can view information about the JVM used for both the Daemon (which executes the build process) and the Launcher JVM (which initiates the Gradle build process) from the command line.

Fixed:
- Unable to debug an 8.9 Gradle build when using TestKit from Gradle 8.8
- Create release notes for the new Java compiler integration with the Problems API
- Gradle 8.8 crashed on MacOS 11.x (8.7 still works as expected)
- Services that depend on ExecutionEngine might not use build cache with 8.9
- Compiler exceptions should be mapped to problems
- Improve docs for --update-locks
- Check if `compileJava` tasks fails because of invalid compiler argument problems
- Gradle 8.8 missing from Kotlin compatibility matrix
- Gradle classes leak into compilation when no dependencies declared
- Mention `:configuration-cache` types moving to `internal` package in the upgrade guide
- Daemon logs should use explicit encoding instead of JVM default
- Move `:configuration-cache` implementation to `internal` package
- Make `ToBeFixedWithIsolatedProject` accessible for type application
- DefaultFileSystemAccess.snapshot sometimes ignoring filter
- Introduce `@ToBeReplacedByLazyProperty` annotation
- ConventionMapping doesn't work correctly for DirectoryProperty and RegularFileProperty after upgrade
- Using a software type with an empty configuration block has no effect in DCL
- FileCollection.elements fail under load.
- Compiler problem reporting causes `IllegalArgumentException` with Java 8 is used with an annotation processor present
- TAPI out of memory in Team city agent
- Report JVM information for Gradle daemon
- Trigger GradleLifecycle callbacks on incremental cache hits
- Start running tests on CI with the Isolated Projects runner
- Cancelling a build can lead to corrupt build cache entries
- Broken Link in CONTRIBUTING.md
- If dependency project has no variants, mention that there are none
- Ensure vanilla Java applications produced by `gradle init` work with Isolated Projects out of the box
- Problem-reporting capable compilation doesn't emit error count
- Precompiled script plugin on Groovy with a package declaration
- Gradle - Build Init Plugin - add a *.jar entry to generated .gitattributes
- Task selection failure reports incorrect file location via Problems API
- String-notated task dependencies shouldn't be flagged as violations
- Remove gradle-org-convention-plugin workarounds
- GroovyJarFile cannot resolve a symlink location in the classpath
- Gradle build deadlocks when transform input is Property<String> computed from an ArtifactCollection via a ValueSource
- Incorrect java warning/error location in new Problems API
- Worker API documentation incorrectly says process isolation creates daemons that persist across builds
- Clarify how to annotate a file that a task may create or may delete
- Project Isolation: PropertyDelegate: Expected unreportedProblemInCurrentCall to be called after enterDynamicCall
- Add debug assertions in dependency resolution when locks should be held
- Add Error Prone annotations to build
- Re-implement replacement for null diagnosticlistener
- The 'wrapper' task removes user-defined settings in the 'gradle-wrapper.properties' file.
- Use `ide-starter` to run IDEA in `:smoke-ide-test`
- Add Deprecation nagging for DefaultFileCollectionDependency#resolve
- Playback model stream on isolated projects build action cache hit
- Introduce smoke test fixing the amount of IP violations observed from Sync with IDEA
- Unify execution engines
- Gradle 8.5 deadlock
- BuildServiceParameters fails with convention plugins
- Support multiple `accepted-public-api-changes.json` files for binary compatibility
- Console should show more information about the file changes that cause a configuration cache entry to be discarded
- Try property upgrade infrastructure on replaced properties
- POM parser does not ignore spaces within `optional` tag and thus resolves differently than Maven
- Race condition between stopping and notifying operation completion listener
- Document best practices for setting conventions on Gradle-provided Properties in tasks
- Eclipse Test Dependency Configuration Overrides Regular Dependency
- Don't cast `VersionConstraint` to `MutableVersionConstraint` in `DefaultMutableMinimalDependency`
- Depending on multiple configurations leads to broken buildship classpath
- Init command does not warn if the current directory is non-empty
- Add an option to set suiteThreadPoolSize for TestNg tests
- More newbie-friendly documentation for the CodeNarc plugin regarding Groovy 3
- Integrate Java compiler with the problems API
- Update Project Isolation documentation page
- Missing link in `Implementing Binary Plugins` doc
- TestKit is broken when tests execute Java compilation and debugging is turned on
- Gradle plugins docs incorrectly specify the settings.gradle
- Dependency configurations should be explained better