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.
Declaring a project dependency
From the course: Gradle for Java-Based Applications and Libraries
Declaring a project dependency
- [Instructor] Over time, projects evolve into complex structures that can become hard to maintain. It's a good idea to break up logic based on functional boundaries with the help of modules. In this video, I want to provide you with a jumpstart on modeling a multi-module build in Gradle. There's a lot to learn about multi-module builds but I will only point out the high-level characteristics important enough to explain project dependencies. Our program is not very complex at the moment. But imagine we would want to break it up into two different aspects. The application that drives the program from the command line and the calculator API that allows us to execute mathematical functions. We'll create two different modules here. App and api. As you can see here, I've already prepared the project hierarchy. The root directory of the project contains the subdirectory's app and api, including the corresponding…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
(Locked)
Mechanics of dependency management1m 59s
-
(Locked)
Declaring a dependency on an external library2m 38s
-
(Locked)
Rendering the dependency tree2m 36s
-
(Locked)
Declaring a project dependency3m 5s
-
(Locked)
Using the Maven Publish plugin to publish a library3m 7s
-
(Locked)
Challenge: Consuming an external dependency1m 44s
-
(Locked)
Solution: Consuming an external dependency3m 29s
-
(Locked)
-
-