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.

Mechanics of dependency management

Mechanics of dependency management

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

Start my 1-month free trial

Mechanics of dependency management

- [Instructor] The Java ecosystem has been around for decades and produce sophisticated production-ready libraries for abstracting aspects, like data management and security. Many of the popular open source libraries are available on Maven Central, a centrally hosted binary repository. Within the Gradle project, you can define a dependency on libraries in Maven Central or any other binary repository. At build time, Gradle's dependency management engine downloads its artifacts, stores them in the local cache for reuse, and adds them to the class path of the project. Gradle calls the scope of a dependency a configuration. You can be very specific about the scope of a dependency. For example, you can express that the dependency is only needed at runtime, but not for the compilation process. Another type of dependency is a project dependency. When application logic becomes overly complex, you will want to separate it based on…

Contents