Description
While using netbeans 11 with lombok 1.18.4, the IDE doesn't generate the builder method for some classes (i.e. it doesn't show in the navigator window). The remaining components are generated (builder class and its methods).
Steps to reproduce
I haven't found any clear pattern in my classes that could be related to this odd behaviour. It seems to happen randomly for classes with the @Builder annotation on the class and no explicit constructor.
I found a workaround : add a constructor and put the annotation on this newly created constructor.
Expected behavior
I expect netbeans to internally generate the builder method, in the same way that maven does.
Version info
I think I may have found a pattern : whenever there is a @Singular on a field, the builder method disappears from the navigator, and all classes that rely on the builder turn red.
Using @Builder.Default causes all kinds of chaos.
Many imports get marked as unused. It marks some properties as unused.
It marks the following assignment as "assignment to itself"
public void setContentType(String contentType) {
this.contentType = contentType;
}
The issue is still present with lombok 1.18.8
Is there any workaround for this problem atm? I'am using netbeans 11.1 and lombok 1.18.10 with maven and the bug is still present.
Tried Netbeans 11.2 and it no longer seems to be broken. 馃帀
ooh, if latest lombok + latest netbeans fixes this, that's great. This is a hard one for us to pick up, as we haven't used netbeans in years, would have to get familiar with it, etc.
Going to park this until a second report that 11.2+ and lombok 1.18.12+ has addressed this.
I tried it with Netbeans 11.3 and Lombok 1.18.8 => OK,
Then I tried it with Netbeans 11.3 and Lombok 1.18.12 => KO
Fails with Lombok 1.18.8 and 1.18.12, Netbeans 11.3 and JDK 11.0.7
As reported by @vicricker removing @Builder.Default from fields, but will cause @Builder to ignore the defaults set (as reported by Lombok).
Most helpful comment
Is there any workaround for this problem atm? I'am using netbeans 11.1 and lombok 1.18.10 with maven and the bug is still present.