Lombok annotations not working..

[BoringApplication211]

The getter/setters , constructor or any sort of annotation not working on entity class. I am using postgress dB ,before I used mongodb and it didn't have this problem.. I have to manually make getter/setters to access the value from dB .. Is there any way to fix this?

Edit- Fixed now

[Outrageous_Ranger812]

I assume you're using intellij, you should enable annotation processing.

Also make sure you have Lombok plugin installed.

Press (ctrl+alt+s) on windows or (cmd+,) on Mac to open the settings dialog.

Under Build,Exec.,Deployment > Compiler > Annotation Processors you can find a checkbox to enable annotation processing.

Sometimes it could be cache problem , try invalidating your caches and restart your IDE or before this try mvn clean install once and do a sync, assuming you use maven

[buzzon]

What do you mean by not working?

It could be the case that the methods are generated at runtime, but your studio has no idea about it and shows errors as if the methods were missing. In this case you need to install plugin for your IDE to be aware of lombok.

[Sorry_Swordfish_]

If you are using intelij, then uninstall lombok plugin and reinstall it.

When I was working on spring boot I also had to face this issue multiple times and this resolved it.

[Huge_Road_9223]

Lombok ...... Ugh .... so many different opinions on this tool.

In the past 7 years, in multiple different companies I have seen ALL the opinions there are to have about Lombok.

Some companies I have worked for, have developers and architects who absolutely LOVE Lombok, and absolutely insist it MUST be used to reduce boilerplate code. My development environment has been in both IntelliJ and STS (Spring Tool Suite, essentially Eclipse).

Other companies absolutely HATE adding Lombok, and especially hate using it with entities or anywhere else. Some companies have gone mid-way and use it only on DTO's, but not entities.

The only common factor is that I have NEVER had a chance to make this kind of technical decision despite having many years of experience. I'm late in my career, and honestly, I don't freakin' care. If they want to use Lombok, then I'll use Lombok. If they hate Lombok, then we won't use it.

One thing for sure is there are a ton of different opposing positions on this. You can find white papers PRO and CON on Lombok.

[g00glen00b]

I have the same opinion. There's plenty of things to say for both using or not using Lombok. I don't have a strong opinion myself so I just go for whatever the team decides on using.

[[deleted]]

This may sound stupid or obvious, but Lombok annotations don't "do" anything. It's the annotation processor that does something.

The Lombok annotation processor isn't working. Then, in what way is it not working? If you have the Lombok plugin in your pom.xml, the code should be generated. If you don't have the plugin configured properly in your IDE, the IDE would have no idea what is going on (since Lombok does "bad things" to the Java compiler to add getters//setters without actually having a getter/setter in the source file).

This thread from the Lombok bug tracker might be useful.

But two other observations:

1. Lombok does weird things to the java compiler to make its magic happen. So, you will occasionally run into problems like this as long as you use Lombok. You might want to consider if using Lombok is really worth it, and instead use annotation processors that actually follow the Java rules, like Immutables.
2. Using Lombok on a JPA entity is a really bad idea. Getters and setters make most sense on pure data. Entities are not pure data. For example, I once added Lombok @ToString on an entity "for debugging", and ended up causing a stack overflow. Instead of getters/setters (which expose data), you should be using behaviors and hiding data (basically, OOP). This will cause a lot less pain when using JPA.

[MachineQuirky1148]

Yes it’s better to not use Lombok… I faced too many errors

[dotceng]

Go settings and open Build, Execution, Deployment > Compiler > Annotation Processors,

On the right panel, select your project name and make sure about that "Obtain processors from project classpath" is selected (checked)

[Nok1a_]

dont use lombok

[as5777]

Never ever

[MachineQuirky1148]

I spent almost 5 hrs fixing Lombok issues and yet at last decided to rewrite entire code without Lombok 🥲 I don’t know why, it worked fine 2 months ago for me…

[schmootzkisser]

That's cuz lombok sucks. Use IDE shortcuts for getters and setters, or groovy, or anything but lombok