Tom Tresansky <******@****.***> 1716911738 -0400

        succeeds(":resolve")
    }

    @ToBeFixedForConfigurationCache(because = "uses Configuration API at runtime")

            .willBeRemovedInGradle9()
            .withUserManual("viewing_debugging_dependencies", "sub:resolving-unsafe-configuration-resolution-errors")
            .nagUser()

        then:
        def expectedDocumentationUrl = DOCUMENTATION_REGISTRY.getDocumentationRecommendationFor("information", "viewing_debugging_dependencies", "sub:resolving-unsafe-configuration-resolution-errors")

[[sec:troubleshooting_dependency_resolution]]
== Debugging dependency resolution

Common dependency resolution issues, such as resolving version conflicts, are covered in <<viewing_debugging_dependencies.adoc#sec:debugging-build-scans,Troubleshooting Dependency Resolution>>.

They can be invoked using the `--scan` options:

----
$ gradle myTask --scan
----

This will give you a link to a web-based report, where you can find <<viewing_debugging_dependencies.adoc#sec:debugging-build-scans,dependency information>> like this:

image::gradle-core-test-build-scan-dependencies.png[Build Scan dependencies report]

[[sec:listing_project_dependencies]]

Gradle takes care of specifying a compatible version of `scala-library` for you.

You can diagnose problems with the version of the Zinc compiler selected by running <<viewing_debugging_dependencies.adoc#sec:debugging-build-scans,dependencyInsight>> for the `zinc` configuration.

.Zinc compatibility table
[%header%autowidth,compact]
|===

    }

    def "demonstrate ambiguous graph variant without single disambiguating value selection failure for project"() {

                        <li><a href="../userguide/library_vs_application.html">Understanding Library and Application Differences</a></li>
                        <li><a href="../userguide/viewing_debugging_dependencies.html">Viewing and Debugging Dependencies</a></li>
                        <li><a href="../userguide/dependency_resolution.html">Understanding Resolution</a></li>

This makes the dependency declarations in your build script and the <<viewing_debugging_dependencies.adoc#sec:identifying_reason_dependency_selection,dependency insight report>> easier to interpret.

.Giving a reason for choosing a certain module version in a dependency declaration
====

This task is similar to the `dependencyInsight` <<viewing_debugging_dependencies.adoc#sec:identifying_reason_dependency_selection,reporting task>>.

By default, `outgoingVariants` prints information about all variants.