lombok plugin annotations

[Rasta341]

uhm, hi :) can someone explain how use lombok annotations like "getter"/"setter" in code?
i check on working project, but in nvim its dont work with just annotations
I had to declare them explicitly for the code to work

oh, yeah, and one more question about supporting some kind of logger like a @slf4j

[s1n7ax]

@Rasta341 What do you mean it doesn't work? What happens when you don't have getters setters defined manually?

[Rasta341]

well, i was try launch simple spring app from this repo: https://github.com/DmitrijsFinaskins/simple-telegram-bot, in intelij idea all works fine, but when i try run in nvim, method getAd() "is not defined", and "log" - a variable of @slf4j highlighted as error... sorry, but right now cant give more information, if u have time, u can try launch code from that repo and looks by yourself :)

aaand thanks very much for answer)

[s1n7ax]

@Rasta341 It works perfectly fine. gd on getter or setter even takes me to the property defined. It's likely that nvim-java is not configured correctly.

[Rasta341]

Oh... well, sorry to bother you, looks like im doing something wrong :) thx for help

[beholders-eye]

@Rasta341 It works perfectly fine. gd on getter or setter even takes me to the property defined. It's likely that nvim-java is not configured correctly.

No it doesn't work... sorry to say that.

[logrusx]

@Rasta341 It works perfectly fine. gd on getter or setter even takes me to the property defined. It's likely that nvim-java is not configured correctly.

No it doesn't work... sorry to say that.

At the moment when it was answered, it may very well have worked. I can confirm it worked a few months ago. However some things have changed since then.

Most notably, Mason has a 2.0 release which changed API.

Either way, it's counter productive to join in an already answered discussions.

Most likely the problem will be solved with the migration to Mason 2.0 is completed. I'm currently stuck on it, but I and I guess others are working on it.

Until then you can use the workaround mentioned in the Mason 2.0 migration issue.

[logrusx]

@beholders-eye here