Lombok issues with NetBeans due to used javac version

[MartinBalin]

Lombok not working in NetBeans

The most probable cause of this is that NetBeans IDE or NetBeans Language Server for VSCode Extension (VSNetBeans) contains newer javac than Lombok supports.

For the purpose of this article NetBeans and VSNetBeans are the same.

Resolution

1. Upgrade Lombok to latest version which might be adapted to latest javac.
   Or
2. Downgrade version of NetBeans to previous release.

Explanation

Internal NetBeans javac (nb-javac) is updated to upcoming JDK release javac in NetBeans development builds before GA release of such JDK.

E.g. After NetBeans 24 was released in Nov 2024 then nb-javac was updated to upcoming JDK 24 javac, using JDK dev builds (before its release in March 2025). JDK 24 javac introduced internal implementation change breaking Lombok GA release at that time.
VSNetBeans 24.9.9 was branched from NetBeans development builds in Jan 2025, still before the release of JDK24 GA and Lombok not adapted to upcoming JDK 24 javac.
As the problem is caused by Lombok using reflection for non API field then NetBeans cannot fix this.
In this case downgrading the IDE to 24.0.0 will help, instance of this problem #8215

There are other cases when upgrading the Lombok helped #5618

[sephiroth-j]

Just commenting for linking the Lombok issue projectlombok/lombok/issues/3814

[matthiasblaesing]

For NetBeans 25 I build d9d0767bba1d383be92baefdf67a1c018a750085 from https://github.com/Rawi01/lombok/commits/jdk24 resulting in lombok-1.18.17+d9d0767b.zip

With that at least most basic usage worked. I only tested @DaTa annotation, as I only have lombok in legacy work projects, not accessible currently). For anyone using maven I suggest to make the lombok version overrideable in your projects:

1. Install the binary after expanding the zip:

mvn org.apache.maven.plugins:maven-install-plugin:3.1.3:install-file\
  -Dfile=lombok.jar\
  -DgroupId=org.projectlombok\
  -DartifactId=lombok\
  -Dversion=1.18.36+d9d0767b\
  -Dpackaging=jar

2. define a property lombok.version and set that to any version you deem right:

    <properties>
        <lombok.version>1.18.36</lombok.version>
    </properties>

3. Declare your dependency with that property (apply to annotationProcessorPaths also, if you use it there)

    <dependencies>
        <dependency>
            <groupId>org.projectlombok</groupId>
            <artifactId>lombok</artifactId>
            <version>${lombok.version}</version>
        </dependency>
    </dependencies>

4. Override that property for your user via $HOME/.m2/settings.xml:

        <profile>
            <id>lombok-fixing</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>
                <lombok.version>1.18.36+d9d0767b</lombok.version>
            </properties>
        </profile>

This way you can switch lombok version centrally and don't interfere with other users. You'll still need to update each project, but at least in between releases or if updating the dependency is probibited for some reason, you can still work.

[mtbadi39]

in spring boot projects, just upgrade lombok to the latest version :

    <properties>
        <lombok.version>1.18.38</lombok.version>
    </properties>

[aritgithub]

I confirm! Solved with Lombok 1.18.38, which adds support for JDK24.

[priyanahata]

I am using nb28 + JDK 25 with

org.projectlombok
lombok
1.18.42
provided

No lombok issues in general and no error badges shown

[SANGWA-JAVA-APPS]

settting this:

<lombok.version>1.18.38</lombok.version>

worked like a charm !!

I am wondering if there are any plans for github copilot for Netbeans, does anyone know ??

[priyanahata]

Yes @SANGWA-JAVA-APPS , copilot is not a model

try this

[priyanahata]

deals with lombok in netbeans in a not make you too angry way