Resolusi Dependensi & Penyimpanan Tembolok

Welcome! In this lesson, we'll dive into how Gradle figures out which libraries your project needs and makes them available. This process is called dependency resolution.

It's crucial for any real-world project, ensuring all necessary components are in place for your code to compile and run.

When you add a library to your project, it can be either a direct dependency or a transitive dependency.

• Direct: Libraries you explicitly list in your build.gradle file.
• Transitive: Libraries that your direct dependencies need to function. Gradle automatically fetches these for you.

Here's a simplified look at how Gradle resolves dependencies:

1. It reads your build.gradle file to find declared dependencies.
2. It checks its local cache for these dependencies and their transitives.
3. If not found, it queries the configured remote repositories (like Maven Central).
4. It downloads the required artifacts and stores them in the cache.

One direct dependency can bring in many others! For instance, if you declare jackson-databind, it also needs jackson-core and jackson-annotations.

Here's a snippet for your build.gradle:

Gradle handles finding jackson-core and jackson-annotations for you.

What if two direct dependencies bring in different versions of the *same* transitive dependency? This is a dependency conflict.

By default, Gradle uses a 'nearest-first' strategy. It picks the version that is 'closest' to the root of your dependency tree. If distances are equal, it often picks the higher version.

To understand what's actually being pulled into your project, the gradle dependencies command is your best friend!

It generates a full dependency tree, showing both direct and transitive dependencies, and highlighting any conflicts.

This command helps you debug resolution issues.

Imagine downloading the same library every time you build your project. That would be slow!

Gradle solves this with its dependency cache. It's a local storage on your machine where all downloaded artifacts (JARs, etc.) are kept.

The dependency cache is typically located in your user's home directory. You'll find it under:

Inside, you'll see folders for different types of artifacts and metadata. You usually don't need to interact with it directly, but it's good to know where it lives!

The dependency cache provides several key benefits:

• Speed: Builds are much faster because artifacts are retrieved locally instead of over the network.
• Offline Builds: You can build your project even without an internet connection, as long as the necessary dependencies are already cached.
• Consistency: Ensures your builds use the same versions of dependencies, promoting repeatable results.

To demonstrate a simple runnable program, here's a basic Groovy application. While it doesn't use external dependencies, understanding how to execute code is fundamental to seeing how Gradle manages dependencies for your actual project code.

Which of the following best describes Gradle's default behavior when resolving conflicts between different versions of the same transitive dependency?

We've covered the essentials of dependency resolution and caching in Gradle. You now understand the difference between direct and transitive dependencies, how Gradle resolves them, and its strategy for handling conflicts.

Crucially, you also learned about the dependency cache and its benefits for faster, more reliable builds. This knowledge is vital for efficient project management!