Movatterモバイル変換


[0]ホーム

URL:


Dependency Resolution

version 9.3.1

Dependency resolution in Gradle can largely be thought of as a two-step process.

First, thegraph resolution phase constructs the dependency graph based on declared dependencies.Second, theartifact resolution phase fetches the actual files (artifacts) for the resolved components:

  1. Graph resolution phase:

    • Driven by declared dependencies and their metadata

    • Uses the request attributes defined by the configuration being resolved

  2. Artifact resolution phase:

    • Based on nodes in the resolved dependency graph

    • Matches each node to a variant and an artifact

dep man adv 1

1. Graph Resolution

During thegraph resolution phase, Gradle constructs adependency graph, which models the relationships between different components and their variants.

SeeGraph Resolution to learn more.

2. Artifact Resolution

Once the dependency graph is resolved, theartifact resolution phase determines whichartifacts (i.e. files) need to be downloaded or retrieved for each variant.

SeeArtifact Resolution to learn more.

You can submit issues directly on Github.
© 2025 Gradle, Inc. Gradle®, Develocity®, Build Scan®, and the Gradlephant logo are registered trademarks of Gradle, Inc.
Gradle
Privacy |Terms of Service

[8]ページ先頭

©2009-2026 Movatter.jp