Gradle Operations TODEPLETE: Difference between revisions
| Line 17: | Line 17: | ||
gradle -q dependencies | gradle -q dependencies | ||
The result is called a ''dependency report''. Any dependency that could not be resolved is marked with FAILED in red color. Dependencies with the same coordinates that can occur multiple times in the graph are omitted and indicated by an asterisk. Dependencies that had to undergo conflict resolution render the requested and selected version separated by a right arrow character. | The result is called a ''dependency report''. Any dependency that could not be resolved is marked with FAILED in red color. Dependencies with the same coordinates that can occur multiple times in the graph are omitted and indicated by an asterisk. Dependencies that had to undergo conflict resolution render the requested and selected version separated by a right arrow character. The dependency report provides the raw list of dependencies but does not explain why they have been selected or which dependency is responsible for pulling them into the graph. These explanations can though be generated, see [[#Identify_Why_a_Specific_Dependency_was_Selected|Identify Why a Specific Dependency was Selected]]. | ||
To display the dependency tree for just one [[Gradle_Concepts#Dependency_Configuration|dependency configuration]]: | To display the dependency tree for just one [[Gradle_Concepts#Dependency_Configuration|dependency configuration]]: | ||
Revision as of 00:54, 8 May 2018
Internal
Overview
Operations
Inspect Dependencies
The full graph of the project's dependencies can be rendered. The selection reason and origin for a dependency can also be displayed.
To display the dependency trees for all dependency configurations of the project, execute:
gradle -q dependencies
The result is called a dependency report. Any dependency that could not be resolved is marked with FAILED in red color. Dependencies with the same coordinates that can occur multiple times in the graph are omitted and indicated by an asterisk. Dependencies that had to undergo conflict resolution render the requested and selected version separated by a right arrow character. The dependency report provides the raw list of dependencies but does not explain why they have been selected or which dependency is responsible for pulling them into the graph. These explanations can though be generated, see Identify Why a Specific Dependency was Selected.
To display the dependency tree for just one dependency configuration:
gradle -q dependencies --configuration <configuration-name>
Identify Why a Specific Dependency was Selected
Command-Line Interface
Tasks
build
Build without tests:
gradle build -x test gradle build -x :some-project:test
projects
gradle projects
tasks
gradle <project-path>:tasks
gradle :module1:tasks
properties
Displays project properties, properties added by various plugins and their default values.
gradle properties