Gradle Dependencies and Dependency Configurations: Difference between revisions
Jump to navigation
Jump to search
Line 21: | Line 21: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
{{Note|Configuration, in this context, does not refer to a configuration file, as in a settings configuration or a build configuration. It refers to named set of dependencies or artifacts, and it can probably thought of as being a concept similar to a Maven [[Maven_Concepts_-_Dependencies#Dependency_Scope|scope]].}} | |||
=Dependency= | |||
=Configuration= | |||
{{Note|Configuration, in this context, does not refer to a configuration file of any sort, as in a settings configuration [[settings.gradle]] or a build configuration [[build.gradle]]. It refers to named set of dependencies or artifacts, and it can probably thought of as being a concept similar to a Maven [[Maven_Concepts_-_Dependencies#Dependency_Scope|scope]].}} |
Revision as of 16:43, 22 October 2020
External
- https://docs.gradle.org/current/userguide/core_dependency_management.html
- https://docs.gradle.org/current/userguide/dependency_management_for_java_projects.html
Internal
TO DEPLETE
Overview
Dependencies for a project can be managed with Project.dependencies(Closure), Project.getDependencies() and the "dependencies" build.gradle DSL element:
dependencies {
// configuration closure
}
Configurations for a project can be managed with Project.configurations(Closure), Project.getConfigurations() and the "configurations" build.gradle DSL element:
configurations {
// configuration closure
}
Dependency
Configuration
Configuration, in this context, does not refer to a configuration file of any sort, as in a settings configuration settings.gradle or a build configuration build.gradle. It refers to named set of dependencies or artifacts, and it can probably thought of as being a concept similar to a Maven scope.