Ben Manes

I suppose you could generate your own report rather than use ours. That can be done using either a custom output formatter or by post-processing the json results. The possible...

We would need a build to debug with, either yours if open sourced or a minimal reproduction. The kotlin plugin does all sorts of hacks into Gradle’s internals, which resolving...

I haven't dug into it, per the frustrations wrt kotlin being a bad citizen and its mistreatments of gradle to break things. Both projects are android-based and require some setup...

I don't have time for helping here. Someone would need to debug the Kotlin plugin and the metadata that is missing. Since Kotlin abuses Gradle inappropriately, I have tried to...

@tlf30 In your case this looks like a regression in Gradle 7.4. Can you open an issue on their side for assistance? The [release notes](https://docs.gradle.org/7.4/release-notes.html) do not hint as to...

Unfortunately if we do that then while no exceptions occur, the dependency is not listed as the configuration is ignored. For robustness due to prior Gradle bugs, misuse of this...

### Gradle 7.3.3 + v42 [Scan result](https://gradle.com/s/a7ngbwnw66rv4) Build file ```groovy apply plugin: 'com.github.ben-manes.versions' apply plugin: 'java-library' buildscript { repositories { mavenLocal() gradlePluginPortal() } dependencies { classpath 'com.github.ben-manes:gradle-versions-plugin:0.42.0' } } repositories...

We log and continue, I think that is a Gradle change to make it a warning.

That is unusual. We resolve through Gradle which has rich dependency management, so rather than poorly reimplement it we delegate and report. The most common issue is that a repository...

Repositories are defined at the project level which configurations are declared on, and we resolve all configurations which hold the dependencies and resolution rules. Since gradle doesn't resolve metadata in...