| Age | Commit message (Collapse) | Author |
|---|
|
removed by eclipse’s organize imports.
|
|
of replacing it with the non-experimental check about 3 years ago when builder moved out of experimental. The check has now been restored.
|
|
installed’ text in the eclipse about dialog.
|
|
|
|
|
|
|
|
`@Builder.Default` static method instead of initializing to null/0/false. This does that, for ecj.
|
|
`@Builder.Default` static method instead of initializing to null/0/false. This does that, for javac.
|
|
|
|
|
|
Fixes #1724
|
|
|
|
documentation review, bugfix for setter auto-presuming chaining even when you didn’t configure it to chain.
|
|
|
|
|
|
|
|
4.8 and above
|
|
|
|
that supports this, without lombok getting in the way.
|
|
|
|
Make the null check exception a little bit more explicit
|
|
|
|
be configured both on the annotation itself and via a config key. This totally breaks compatibility with the previous lombok release, but, hey, it’s in experimental and it’s been one week. This is better.
|
|
- The class has a parent class
- There is an explicit XxxArgsConstructor annotation that would generate
a no-args constructor
Fixes #1703, fixes #1704, fixes #1712
|
|
lombok’s log annotations.
|
|
onlyExplicitlyIncluded, didn’t work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 9ee2491427f1522a7689d1c28a816294bcff315b.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Currently it is "NullPointerException: someFieldName" and that is not very
telling as to the reasons this exception is thrown.
|
|
|
|
|
