From the course: Gradle for Java-Based Applications and Libraries

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Rendering the dependency tree

Rendering the dependency tree

From the course: Gradle for Java-Based Applications and Libraries

Start my 1-month free trial

Rendering the dependency tree

“

- [Instructor] As the project evolves over time, more and more dependencies might be added to support the project by reusing existing functionality. There are good reasons for wanting to get a better overview of the declared dependencies in the bulk script and their transitive dependencies they pull in automatically. Gradle offers the task named dependencies to render the full tree of dependencies for all configurations available in the project. At this time, the project declares a single dependency, Apache commons-cli. Let's render the dependency tree and see if we can find it. As you can see here, dependencies are grouped by configurations. We added the dependency with the gaff commons-cli:commons-cli:1.4 to the configuration called implementation. The dependency does not provide any transitive dependencies, otherwise you would see them rendered underneath. In the output of the command, you can also see that the same…

Contents