Скачать или смотреть Fixing classNotFoundExceptions in Gradle Multi-Module Projects: An Easy Guide

Struggling with `classNotFoundExceptions` in a Gradle multi-module project? Discover how to compile sub-modules successfully and create a monolithic JAR without dependencies.
---
This video is based on the question https://stackoverflow.com/q/63933696/ asked by the user 'Swapnil Kotwal' ( https://stackoverflow.com/u/1665592/ ) and on the answer https://stackoverflow.com/a/63952917/ provided by the user 'Swapnil Kotwal' ( https://stackoverflow.com/u/1665592/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Gradle multi-module project compilation fails with "classNotFoundExceptions" from dependencies mentioned in sub-modules

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Fixing classNotFoundExceptions in Gradle Multi-Module Projects: An Easy Guide

In a complex Gradle multi-module Java project, it’s not uncommon to encounter compilation issues, particularly classNotFoundExceptions. This can be frustrating, especially when individual modules compile without issues, but the project fails when building from the root. If you've found yourself in this situation, don’t worry! We’re here to guide you through solving this problem seamlessly.

Understanding the Problem

Let’s begin by clarifying the core issue at hand: when you attempt to run ./gradlew compileJava from the root of your multi-module project, it fails due to classes not being found within specified dependencies. Conversely, running ./gradlew core-module:compileJava works perfectly fine. This is an indicator that while the sub-modules are set up correctly, the root project’s configuration is leading to compilation failures.

Common Causes

Here are a couple of reasons this might happen:

Local JAR References: The project may be referring to local JAR files that are not being recognized in the root project context.

Source Set Configuration: The sourceSets in the root build.gradle file might be incorrectly configured, leading to failures when attempting to reference classes across sub-modules.

Step-by-Step Solution

To remedy the issue and successfully compile the entire project while creating a monolithic JAR without dependency jars, follow these steps:

1. Adjust Your jar Task

Include the following configuration in your root build.gradle to create a single JAR file from all sub-modules while ensuring all necessary classes are included:

[[See Video to Reveal this Text or Code Snippet]]

2. Verify Your Source Sets Configuration

Ensure that your source sets section in the root build.gradle is correctly referencing the directories of the sub-modules. The configuration should not just point to the source directories; it should properly establish dependencies between them to ensure visibility of classes. For example:

[[See Video to Reveal this Text or Code Snippet]]

3. Build Your Project

Once you've adjusted your jar task and confirmed that your source sets are properly configured, you can proceed to build the project. Use the command below from the root of your multi-module setup:

[[See Video to Reveal this Text or Code Snippet]]

This should compile the entire project and produce a monolithic JAR file that incorporates all classes across sub-modules.

Conclusion

By carefully configuring the jar task and verifying your sourceSets, you can effectively resolve compilation issues in a Gradle multi-module project. Remember that the configurations and dependencies in multi-module setups can become complex, so it’s important to manage them diligently. Following the steps outlined above should lead to a successful build process without encountering classNotFoundExceptions.

If you find this guide helpful or have any questions, feel free to reach out or leave your comments below! Happy coding!