- PLATFORM: JDK18 support added. .
- PLATFORM: Using ecj and maven? There's now a command line option to integrate lombok into your build chain. .
- FEATURE: `@ToString` has an annotation parameter called `onlyExplicitlyIncluded`. There's now a config key `lombok.toString.onlyExplicitlyIncluded` to set this property as well. .
- FEATURE: Turning a field named `uShape` into a getter is tricky: `getUShape` or `getuShape`? The community is split on which style to use. Lombok does `getUShape`, but if you prefer the `getuShape` style, add to `lombok.config`: `lombok.accessors.capitalization = beanspec`. Pull Request #2996. Thanks @YonathanSherwin!
- FEATURE: You can now use `@Accessors(makeFinal = true)` to make `final` getters, setters, and with-ers. .
- BUGFIX: Various save actions and refactor scripts in eclipse work better. .
- BUGFIX: Eclipse projects using the jasperreports-plugin will now compile. .
- BUGFIX: inner classes in `@UtilityClass` classes were broken in JDK9+. .
- BUGFIX: Delomboking code with `@Builder.Default` in it would generate different code vs lombok itself. .
- BUGFIX: Combining `@NonNullByDefault` and `lombok.addNullAnnotations` would generate two `@Nullable` annotations and thus generate a compiler error. . Thanks @JohnPaulTaylorII!
- BUGFIX: Null analysis in eclipse was broken for incremental builds. .
- BUGFIX `VerifyError` would show up in the latest eclipse release when using various refactor scripts. .
- BUGFIX: The various `@Log` annotations can now be placed on inner enums and records. .
- SECURITY: A widely reported security issue with log4j2 (CVE-2021-44228) has absolutely no effect on either lombok itself nor does usage of lombok on its own, or even the usage of lombok's `@Log4j2`, cause any issues whatsoever: You have to ship your own log4j2 dependency in your app - update that to 2.17 or otherwise mitigate this issue (see the CVE page). To avoid unneccessary warnings from dependency checkers, our dep on log4j2, which is used solely for testing, isn't shipped by us, and cannot be exploited in any way, has been updated to 2.17.1.
- IMPROBABLE BREAKING CHANGE: Lombok now understands a few more annotations that imply "this field should not ever contain a null reference". Lombok will thus copy some of these new annotations e.g. to generated getters and the like. Pull Request #2904