matthiasblaesing commented on issue #7111:
URL: https://github.com/apache/netbeans/issues/7111#issuecomment-1963039324
> Is Lombok breaking all IDEs or just NB?
Don't know. Eclipse might or might not have been affected as they have their
own javac, where I don't know how lombok hooks into that.
> Clearly, a user's expectation would be that the Java version specified in
the project settings would have to match the Lombok version specified in the
project settings. I find it a surprising requirement that I have to match
project dependencies to undocumented internal IDE dependencies. The NB
documentation states that the IDE runs with the JDK I specify in the
netbeans.conf file.
NetBeans uses a copy of the javac to parse java code and handle annotation
processing, class parsing and such. That javac needs to be current to support
new features. In the past NetBeans used the javac of the JDK it was running on,
but reality is, that the javac API changes often enough, that this causes major
overhead and was not stable. The error you saw is caused by the fact, that the
javac in NetBeans is to new to use the old lombok version. You would have seen
the same problem if you had tried to compile your code on an up-to-date JDK
(aka 21).
For me the discussion ends at this point.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
