Resolving Issues with Lombok in module-info.java Setup for Java Libraries

---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

The Problem

Consider a situation where you are working with a Java library that heavily uses Lombok and generics. Upon running your Maven package, you find yourself inundated with errors, particularly the following:

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

The error message indicates a missing symbol for the method .builder() within a class that leverages Lombok's @ SuperBuilder. This issue often stems from the way the Lombok library interacts with the Java module system, particularly how annotation processing is configured.

Code Overview

The following snippets illustrate a simplified scenario leading to the error:

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

The Response class is defined as follows:

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

The Solution

The primary issue arises from the configuration of the Maven Compiler Plugin. To resolve the problem, modifying the plugin's setup to include annotationProcessorPaths will provide Lombok the necessary context during compilation.

Step-by-step Modification

Modify the plugin's configuration to include annotationProcessorPaths as shown below:

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

Explanation of Changes

annotationProcessorPaths: This addition informs the compiler about the paths for annotation processors. Without this, Lombok's annotations (like @ SuperBuilder) may not function correctly, leading to errors like the one you encountered.

Conclusion

Following the steps outlined above should resolve the issue of missing symbols and allow you to leverage the full power of Lombok in your modular Java library.

If you experience further issues, don't hesitate to troubleshoot your annotations and ensure all necessary dependencies are correctly set up in your project's modular architecture.