Age | Commit message (Collapse) | Author |
|
overzealous as to what it marks as ‘generated’, if you manually write the builder class and add some elements, you’d get crazy errors on those.
|
|
|
|
alternative take on how to ‘fix’ null-collections and singular/toBuilder.
|
|
janrieke-wildcardsSingularFix
|
|
reflective access via a class that uses sun.misc.Unsafe to arrange access. From the nqzero permit-reflect library.
|
|
|
|
correct issueManagement declaration in maven POM
|
|
Added Spring NonNull and Nullable annotations
|
|
Customizable SuperBuilder
|
|
these as unit tests someday.
|
|
Motivation
The published maven POM for lombok refers to Google Code for issue
management. Google code is no longer active.
Changes
- replace with github issues for issue management
|
|
|
|
way javac/java support it.
|
|
(module-info) style projects.
|
|
|
|
annotated. Fixes #1772
|
|
|
|
Fix code example for @UtilityClass
|
|
|
|
|
|
|
|
|
|
other build-related issues.
|
|
longer throws NPE.
|
|
|
|
|
|
|
|
|
|
janrieke-superToBuilder
|
|
|
|
|
|
testing that the compiler emits warning/error messages.
|
|
unless you know what you’re doing as it skips a few important steps.
|
|
to an error in the build file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and for example their use on the typearg in a collection type which is being `@Singular`-ized.
|
|
|