https://docs.gradle.org/current/userguide/dependency_management_terminology.html
Dependency Management Terminology
A file or directory produced by a build, such as a JAR, a ZIP distribution, or a native executable. Artifacts are typically designed to be used or consumed by users or other projects, or deployed to hosting systems. In such cases, the artifact is a single
docs.gradle.org
https://docs.gradle.org/current/userguide/core_dependency_management.html
Dependency Management
Software projects rarely work in isolation. Projects often rely on reusable functionality from libraries. Some projects organize unrelated functionality into separate parts of a modular system. Dependency management is an automated technique for declaring,
docs.gradle.org
https://docs.gradle.org/current/userguide/declaring_repositories.html
Declaring repositories
When searching for a module in a repository, Gradle, by default, checks for supported metadata file formats in that repository. In a Maven repository, Gradle looks for a .pom file, in an ivy repository it looks for an ivy.xml file and in a flat directory r
docs.gradle.org
https://docs.gradle.org/current/userguide/declaring_dependencies.html
Declaring dependencies
Configurations are intended to be used for a single role: declaring dependencies, performing resolution, or defining consumable variants. In the past, some configurations did not define which role they were intended to be used for. A deprecation warning is
docs.gradle.org
https://docs.gradle.org/current/userguide/library_vs_application.html
Understanding the difference between libraries and applications
Whenever, as a developer, you decide to include a dependency, you must understand that there are consequences for your consumers. For example, if you add a dependency to your project, it becomes a transitive dependency of your consumers, and therefore may
docs.gradle.org
https://docs.gradle.org/current/userguide/viewing_debugging_dependencies.html
View and Debug Dependencies
A project may request two different versions of the same dependency either directly or transitively. Gradle applies version conflict resolution to ensure that only one version of the dependency exists in the dependency graph. The following example introduc
docs.gradle.org
https://docs.gradle.org/current/userguide/dependency_resolution.html
Understanding dependency resolution
Gradle contains a highly sophisticated dependency caching mechanism, which seeks to minimise the number of remote requests made in dependency resolution, while striving to guarantee that the results of dependency resolution are correct and reproducible. Th
docs.gradle.org
https://docs.gradle.org/current/userguide/dependency_verification.html
Verifying dependencies
The local keyring files (.gpg or .keys) can be used to avoid reaching out to key servers whenever a key is required to verify an artifact. However, it may be that the local keyring doesn’t contain a key, in which case Gradle would use the key servers to
docs.gradle.org
'Android > Gadle' 카테고리의 다른 글
| Project 객체의 속성 (0) | 2024.03.13 |
|---|---|
| Gradle User Manual (0) | 2024.03.13 |
| Android Gradle plugin API reference (0) | 2024.03.13 |
| 그레이들 테스크 실행 (0) | 2024.03.13 |
| 그레이들 Gradle (0) | 2024.03.13 |
