Dear team, I have run ./gradlew dependencies on my project. My project is a multi-module project. However, in my dependencies result it shows this. My util module is failed. But my project can be build successfully.

+--- project :network
+--- project :util FAILED
+--- project :model

I have updated my kotlin version, i refer to this https://github.com/gradle/github-dependency-graph-gradle-plugin/issues/140#issuecomment-2230255380. However, it still failed.

In which configuration is that shown?

Sorry, which configuration you are referring? Can you give an example.

The task displays all configurations and their resolution result

oh it is : implementationDependenciesMetadata

Well, that's something by the Kotlin Gradle Plugin. Could well be that this is also not properly resolvable in all cases. 🤷‍♂️ Maybe @Tapchicoma can say something about it, but as long as building works, you should probably not care too much. 🤷‍♂️

Indeed our experience is as well that such dependencies metadata configurations are not resolvable, see https://github.com/oss-review-toolkit/ort/blob/15dcd7b5d80b6ea0429f799ef363321208c[…]managers/gradle-plugin/src/main/kotlin/GradleModelExtensions.kt

Maybe the same bad idea they had they had with the sources, registering a resolvable configuration that is known to not resolve properly, breaking other things that try to work on all resolvable configurations, ... For the sources at least they refactored it, that's where the "update Kotlin" advice came from in the ticket linked in OP

AFAIK we fixed resolution results in some recent Kotlin versions. @Amalina which Kotlin version you project is using? Could you share a build scan?

Did you fix it for all? I know you fixed it for sources, but this is about the

...Metadata

configuration

Should be for all - if not in Kotlin 2.1.0 - better to create a Kotlin issue

@Vampire, yeah I don't want to care about it too much. But my project gitlab pipeline for gymnasium-maven-dependency_scanning has failed. It shows this "Project has unresolved dependencies". I have updated the Kotlin version as they suggested, but Maven dependency scanning still failing. In this case, i should contact gitlab support already?

Try the 2.1.0 release candidate. :-)