This might not help you for now, but I also came across issues in my
project which uses lombok. However it was not NetBeans specific. I wanted
to upgrade to a new JDK, but a lot of tests were failing, upgrading lombok
itself didn't resolve it. So I decided to take the long way and delomboked
my sou
Bump. Anyone, any suggestions?
> On Dec 10, 2019, at 12:29 PM, Alvin Thompson wrote:
>
> Hi,
>
> I’ve been having a problem where in one of my projects, NetBeans is
> constantly highlighting references to methods generated by Lombok as an
> error. However, it’s not a "method not found error"
Yep, deleting the cache fixes it in this case as well, but it’s only temporary.
> On Dec 10, 2019, at 2:56 PM, Tim Boudreau wrote:
>
> Deleting the cache from the userdir fixes it (nothing else does) - it seems
> like the indexing plumbing gets something stuck in its craw that stays there
> f
> On Dec 10, 2019, at 2:56 PM, Tim Boudreau wrote:
>
> P.S. Don't use beans, for anything. I'd highly recommend finding a framework
> that encourages absolutely everything that possibly can be to be immutable -
> the final keyword in Java is one of the powerful bug-prevention tools in the
>
FWIW, I have had similar problems when developing modules referencing code
generated by the annotation processors for Antlr - doesn't happen often for
me, but it does happen. Deleting the cache from the userdir fixes it
(nothing else does) - it seems like the indexing plumbing gets something
stuck
Hi,
I’ve been having a problem where in one of my projects, NetBeans is constantly
highlighting references to methods generated by Lombok as an error. However,
it’s not a "method not found error" as you’d expect, but rather the opposite—it
claims that the method is ambiguous because there are t
