I worked with Lombok without any problems until Today, when my Intellij was automatically updated to the latest version 2020.3 30th, November build. After that, any Lombok annotations is not recognised anymore.
My Java project still build from command line with Maven but annotations are completely ignored in the project and cannot run any unit tests manually.
Things I tried so far:
Nothing worked. What could have happened? Any idea on what I can try to do?
As of IntelliJ version 2020.3, we don't need to configure the IDE to use Lombok anymore. The IDE comes bundled with the plugin. Also, the annotation processing will be enabled automatically.
Eclipse 2020-12 (Eclipse 2020-12 Java) does not support Lombok. It runs fine, but the IDE shows errors for all Lombok generates getters/setters. The previous version of Eclipse work fine. You have to install lombok on your installation, otherwise Eclipse will not be able to handle the Lombok-Annotations.
I worked with Lombok without any problems until Today, when my Intellij was automatically updated to the latest version 2020.3 30th, November build. After that, any Lombok annotations is not recognised anymore.
java: You aren't using a compiler supported by lombok, so lombok will not work and has been disabled. Any project compiled in IntelliJ is affected. IntelliJ is now wrapping the ProcessingEnvironment in a Proxy.
The Lombok plugin is now built-in. IntelliJ IDEA can download shared indexes for popular Maven libraries directly from JetBrains’ servers. If you develop plugins with an IntelliJ Platform SDK, shared indexes will be downloaded automatically.
Lombok plug-in author now works for JetBrains and Lombok plug-in is bundled with IntelliJ IDEA, so you don't need to install it separately or update it manually like before. It will be always compatible with the current IDE version from now on. This issue cannot be fixed by the plug-in update. No. These two are unrelated. See my comments above.
To summarize go to IntelliJ Preferences (Cmd + ,)
Preferences -> Build, Execution, Deployment -> Compiler
search for this option:
User-local build process VM options (overrides Shared options):
and add this value:
-Djps.track.ap.dependencies=false
A work around is here, until they fix the actual problem:
https://youtrack.jetbrains.com/issue/IDEA-250718#focus=Comments-27-4418347.0-0
(see screenshoot for IJ fix)
My problem was related to my lombok version
Before upgrade my IntelliJ to 2020.03 my lombok version was 1.18.10
and the lombok plugin 0.32-EAP
After upgrade my lombok dependency to 1.18.16
it start work again without any issues. Looks like the plugin is not bundled yet in the community edition.
I don't if is necessary, but my first action was to uninstall the plugin when I read the README on Lombok Plugin repo
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With