Louis Jacomet

The issue is in the backlog of the relevant team and is prioritized by them. *** Thank you for taking the time to provide reproducer steps. We know how hard...

Hey, The original failure was about the JAR, not metadata: `One artifact failed verification: gradle-enterprise-gradle-plugin-3.15.1.jar` Then after the update, it looks like it complains that the checksum is missing. Can...

Hey @bmuschko, I am sorry, but I cannot reproduce that failure. With the verification metadata file you shared, a project that only applies the scans plugin in settings can run...

Adding our automation for dealing with missing reproducer. The ideal way to provide a reproducer is to leverage our [reproducer template](https://github.com/gradle/gradle-issue-reproducer). You can also use [Gradle Project Replicator](https://github.com/android/project-replicator) to reproduce...

Hey @bmuschko, I believe there is a misunderstanding here. `false` will turn off doing verification for `.pom` and `.module` files when pulling dependencies. There is no way to disable _artifact_...

This feature request is in the backlog of the relevant team and is prioritized by them. *** If you are interested in contributing to Gradle, this issue is actionable and...

Thank you for your contribution! This PR has a valid DCO and meaningful change. The relevant team for this area will confirm the design of the implementation choices.

@bot-gradle merge

Damn, that's not good. I am not sure when I'll have the time to follow up properly on this, especially if a change is needed on the Gradle side.

This is caused by a capability conflict ordering issue in Gradle. A workaround is to make sure that the dependency that resolves the conflict is seen before any dependency it...