After upgrading to JDK 21, I have the following compilation error in my Spring Boot project:
Fatal error compiling: java.lang.NoSuchFieldError:
Class com.sun.tools.javac.tree.JCTree$JCImport does not have member field 'com.sun.tools.javac.tree.JCTree qualid'
The culprit is Lombok. The minimal Lombok version compatible with JDK 21 is 1.18.30.
This implies that the minimal Spring Boot version is 3.1.4, unless you want to meddle with the Spring Boot autoconfiguration and set the Lombok version in your project differently from the Spring Boot BOM defined in spring-boot-dependencies.
>= 3.1.4. Others who are not so lucky and have to keep their Spring Boot version lower, overrode their dependency and added Lombok >= 1.18.30. "How to manage Maven dependency" is another topic and as such has been answered in StackOverflow multiple times, so I guess that in the case of this particular error pointing out the root cause is enough for the answer :) –
Stat I followed the first answer from here and I made the following changes. Previously, it brought the Lombok version 1.18.20 as default, and I needed to feed the latest which resolved the issue for me when I moved from Spring Boot 2.XX to 3.3.3.
When doing a mvn dependency:tree, you can see from where the lower version is coming from and if you want exclude that and new or just add new and check one more time. Still it's pulling the older version. If not, just add a new one like below. So far there isn't any issue with this solution.
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.30</version>
<scope>provided</scope>
</dependency>
When I received this error, my pom.xml looked like this:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.5.5</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
<!-- ... -->
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<!-- ... -->
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludes>
<exclude>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</build>
</project>
I modified it to look like this, and the error went away:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.5.5</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
<!-- ... -->
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<!-- ... -->
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<!-- <optional/> Removed -->
<version>1.18.30</version> <!-- Added -->
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludes>
<exclude>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</build>
</project>
I found the answer in this GitHub comment, and you can find more background information there, too. Another user states this is a workaround, not a solution, but I haven't dug into it deep enough to form my own opinion.
I'm throwing my own answer into the ring because I feel it's more comprehensive than the others: It shows more of the pom.xml. Others include an excerpt of the pom.xml and assume the rest of it looks a specific way.
For example, one answer tells you to add a version number to lombok without telling you to exclude it from spring-boot-maven-plugin. Another answer has the opposite problem.
You don't show what your other dependencies' versions are, namely Sprint Boot. Good point. I've included that in an edit. For context, this pom.xml was not created by me which is why I'm using such an old version. ...whenever I meddled with transitively dependent artefact, it backfired badly... I agree it's not ideal. Personally, it's never caused a huge issue when I run into those scenarios. Maybe I'm lucky, but they have been pretty easy to troubleshoot. Plus, in the context of this pom.xml, upgrading SB from 2.0 to 3.0 might be a project in it of itself. –
Stace Use the Lombok exclude in the Spring Boot Maven plugin and it should work for JDK 21.
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludes>
<exclude>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
<scope>provided</scope> . Lombok is properly configured in Spring Boot and is not included in your project in runtime. Not each "common pattern" is a good patter. –
Stat I also had today this problem after changing from Java 19 -> 21.
I also upgraded Spring boot version from 3.0.4 -> 3.2.3
I followed recommended approach to only increase lombok version to 1.18.30. Then error disapeared but I had issues with beans and dependencies so I returned spring boot version back to 3.0.4 and all works fine with java 21 and lombok.
I also tried to test which version of spring boot is making problem so I went from 3.0.4 to 3.2.2 and 3.1.8 is fine but from 3.2.2 is making problems with dependencies. I am using webflux from project reactor, so I will now stick with 3.1.8.
So there is also probably some change in last spring boot release that causes compatible issues with lombok I guess. I followed this article https://1kevinson.com/nosuchfielderror-jcimport-does-not-have-member-field-jctree-qualid/ below I cut how I have it in my pom.xml, I use Maven.
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>3.0.4</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
.....
<properties>
<java.version>21</java.version>
</properties>
.....
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
<version>1.18.30</version>
<scope>provided</scope>
</dependency>
...
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludes>
<exclude>
<groupId>org.project-lombok</groupId>
<artifactId>lombok</artifactId>
</exclude>
</excludes>
</configuration>
</plugin>
I was facing same issue. And i had also make it 1.18.30. But still it was not working. In that i was making mistake in annotationProcessorPaths. In that i had also dependency of projectlombok but version given 1.18.28 and it was not working. So final change below working fine.
Spring boot 3.2.2
Java 21
projectlombok 1.18.30
<org.projectlombok.version>1.18.30</org.projectlombok.version>
<annotationProcessorPaths>
<path>
<groupId>org.mapstruct</groupId>
<artifactId>mapstruct-processor</artifactId>
<version>${org.mapstruct.version}</version>
</path>
<path>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>${org.projectlombok.version}</version>
</path>
<path>
<groupId>org.projectlombok</groupId>
<artifactId>lombok-mapstruct-binding</artifactId>
<version>${lombok-mapstruct-binding.version}</version>
</path>
</annotationProcessorPaths>
${org.projectlombok.version} is NOT the default spring boot lombok version property. Use ${lombok.version} if your idea is to overload the value from spring-boot-dependencies. –
Stinky Note that if you still get the error after updating to 1.18.30 in IntelliJ even after you rerun the build, its because IntelliJ has some cache which is still picking up the previous lombok version. Try one of these in that case:
This work for me
Replace this:
...
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.XX</version>
<scope>provided</scope>
</dependency>
...
With this:
...
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.30</version>
<scope>provided</scope>
</dependency>
...
Actually, even I've been getting the same error but for me, all I need to do was to change the Java JDK version and the Language level in the Project Structure (I had the following configuration in my project :-
I have faced this problem before, and that's because Lombok has compatibility issues with any Java JDK lower than 21 in any other version different from:
1.18.30
Just go into your pom file and change it to:
<!-- Lombok -->
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.30</version>
<scope>provided</scope>
</dependency>
© 2022 - 2024 — McMap. All rights reserved.