Why Lombok Fails After an IDEA Upgrade and How to Fix It

After upgrading IntelliJ IDEA, Lombok annotations may stop working and cause compilation errors, but updating Lombok to version 1.18.14 or later and adjusting IDE settings can restore functionality for Java and Spring Boot projects.

Programmer DD
Programmer DD
Programmer DD
Why Lombok Fails After an IDEA Upgrade and How to Fix It

After upgrading IntelliJ IDEA, many users encounter Lombok annotations not being processed, resulting in compilation errors such as “cannot find symbol log”. The IDE also warns that the current compiler does not support Lombok.

The root cause is the IDEA version; updating Lombok to 1.18.14 or later resolves the issue. For Maven projects add the following dependency:

<dependency>
  <groupId>org.projectlombok</groupId>
  <artifactId>lombok</artifactId>
  <version>1.18.14</version>
  <scope>provided</scope>
</dependency>

If you use Spring Boot, the Lombok version is managed automatically; older Spring Boot versions (e.g., 2.1.3) may still bring an older Lombok (1.18.6) that causes the problem.

Additional troubleshooting steps:

Ensure the Lombok plugin is installed and enabled.

In Settings → Build, Execution, Deployment → Compiler → Annotation Processors, check “Enable annotation processing”.

Add the JVM option -Djps.track.ap.dependencies=false to the compiler configuration.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

JavaSpring BootIntelliJ IDEAAnnotation Processing
Programmer DD
Written by

Programmer DD

A tinkering programmer and author of "Spring Cloud Microservices in Action"

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.