On Wed, 5 Aug 2026 22:09:09 GMT, Michael Strauß <[email protected]> wrote:
> Loading the project in IntelliJ fails during Gradle synchronization with > dependency verification errors for Groovy 4.0.28 artifacts. A normal > command-line task such as `gradlew help` does not reproduce the problem > because it does not request source artifacts for Gradle’s bundled Groovy > libraries. The underlying cause is that the Gradle 9.2 upgrade introduced > Groovy 4.0.28, but the committed verification metadata was never expanded for > the metadata files used specifically during IDE source resolution. > > When IntelliJ imports the project with source downloading enabled, Gradle > attempts to attach sources for its local Groovy dependencies. Gradle performs > this resolution through its internal repository named Gradle Libs. The > project enables verification of dependency metadata: > > <verify-metadata>true</verify-metadata> > > > Source JARs are already trusted by the existing `*-sources.jar` rule. > Resolving those JARs, however, also requires Gradle module metadata and the > Groovy BOM metadata. These .module and .pom files are not present in > verification-metadata.xml, so Gradle rejects them. > > This problem is fixed by adding checksums for the module metadata of every > Groovy 4.0.28 library bundled with Gradle 9.2. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). This pull request has now been integrated. Changeset: a141fc37 Author: Michael Strauß <[email protected]> URL: https://git.openjdk.org/jfx/commit/a141fc3747b6f1041bad59ed17b6e8eca88868a8 Stats: 7 lines in 2 files changed: 5 ins; 0 del; 2 mod 8389847: Gradle project import fails dependency verification Reviewed-by: mhanl, arapte ------------- PR: https://git.openjdk.org/jfx/pull/2247
