build(deps): bump lombok from RELEASE to 1.18.24

[dependabot]

Bumps lombok from RELEASE to 1.18.24.

Release notes

Sourced from lombok's releases.

v1.18.16

• BUGFIX: Version 1.18.14 could not be installed in Eclipse, it would break Eclipse.
• BREAKING CHANGE: mapstruct users should now add a dependency to lombok-mapstruct-binding. This solves compiling modules with lombok (and mapstruct).
• IMPROBABLE BREAKING CHANGE: The generated hashcode has changed for classes that include both primitive fields and reference fields.
• FEATURE: Similar to @Builder, you can now configure a @SuperBuilder's 'setter' prefixes via @SuperBuilder(setterPrefix = "set") for example. We still discourage doing this. [Pull Request #2357](rzwitserloot/lombok#2357).
• FEATURE: If using @Synchronized("lockVar"), if lockVar is referring to a static field, the code lombok generates no longer causes a warning about accessing a static entity incorrectly. [Issue #678](rzwitserloot/lombok#678)
• FEATURE: @Jacksonized on a @Builder or @SuperBuilder will configure Jackson to use this builder when deserializing. [Pull Request #2387](rzwitserloot/lombok#2387) thanks to @​JanRieke. @​Jacksonized documentation.
• FEATURE: The checkerframework support has been updated; the relevant annotations were renamed in checkerframework's APIs, lombok now generates the annotations according to their current API names.
• PLATFORM: Added support for compiling projects with OpenJ9 [Pull Request #2437](rzwitserloot/lombok#2437)
• PLATFORM: Improved support for recent JVM/javac versions (14 and 15) and new language features.
• PERFORMANCE: Several performance improvements during parsing/compilation, both using javac and Eclipse. Thanks @​Rawi01!
• PERFORMANCE: The generated equals method will first compare primitives, then primitive wrappers and then reference fields. Manual re-ordering is possible using @Include(rank=n). [Pull Request #2485](rzwitserloot/lombok#2485), [Issue #1543](rzwitserloot/lombok#1543)
• BUGFIX: Delombok prints the first this parameter. [Issue #2444](rzwitserloot/lombok#2444)
• BUGFIX: Using val in combination with values whose generics include wildcards that reference themselves would cause a StackOverflowError in javac. [Issue #2358](rzwitserloot/lombok#2358).
• BUGFIX: Using @SuperBuilder on a class that has some fairly convoluted generics usage would fail with 'Wrong number of type arguments'. [Issue #2359](rzwitserloot/lombok#2359) [Pull Request #2362](rzwitserloot/lombok#2362)
• BUGFIX: Various lombok annotations on classes nested inside enums or interfaces would cause errors in eclipse. [Issue #2369](rzwitserloot/lombok#2369)
• BUGFIX: Trying to add @ExtensionMethods with exactly 2 arguments would fail in eclipse. [Issue #1441](rzwitserloot/lombok#1441) [Pull Request #2376](rzwitserloot/lombok#2376) thanks to @​Rawi01.
• BUGFIX: Javac sets incorrect annotated type on with methods. [Issue #2463](rzwitserloot/lombok#2463)

v1.18.14

• Don't use this version. It is broken. Changes are listed under 1.18.16

v1.18.12

• PLATFORM: Support for JDK13 (including yield in switch expressions, as well as delombok having a nicer style for arrow-style switch blocks, and text blocks).
• PLATFORM: Support for JDK14 (including pattern match instanceof expressions).
• FEATURE: In lombok.config it is possible to import other config files, even from a .zip or .jar.
• FEATURE: You can now configure a builder's 'setter' prefixes via @Builder(setterPrefix = "set") for example. We discourage doing this, but if some library you use requires them, have at it. [Pull Request #2174](rzwitserloot/lombok#2174), [Issue #1805](rzwitserloot/lombok#1805).
• FEATURE: If you use @Builder's @Singular, a plural form is also generated, which has the effect of adding all elements in the passed collection. If you pass a null reference, this would result in a message-less NullPointerException. Now, it results in that exception but with a useful message attached (uses the same config as @NonNull), or alternatively via a parameter on @Singular, you can choose to ignore such a call (add nothing, return immediately); this can be useful when deserializing (e.g. Jackson JSON) and JPA/Hibernate code. [Issue #2221](rzwitserloot/lombok#2221). singular documentation.
• FEATURE: Tired of being unable to use @javax.annotation.ParametersAreNonnullByDefault or @org.eclipse.jdt.annotation.NonNullByDefault because then the equals method that lombok generates isn't valid? Fret no more; lombok can now add nullity annotations where relevant. Set the flavour of nullity annotation you prefer in your lombok.config. Applies to the return value of toString, withX, chainable setX, static constructors, build, builder, etcetera, and the parameter of equals, canEqual, and the plural form of @Singular marked fields for builder classes. [Issue #788](rzwitserloot/lombok#788)
• BUGFIX: If using the sonarlint plugin in eclipse for projects bound to sonarcloud, you now no longer get internal errors on sonarlint processing. [Issue #2351](rzwitserloot/lombok#2351)
• BUGFIX: lombok.experimental.Wither has been deprecated (it has been renamed to lombok.With). However, the intent is that lombok still handles the old annotation in case you haven't updated your lombok dep yet. However, only a star import on lombok.experimental.* worked; an explicit one would cause lombok to not generate any with method. [Issue #2235](rzwitserloot/lombok#2235)
• BUGFIX: Referring to an inner class inside the generics on a class marked with @SuperBuilder would cause the error wrong number of type arguments; required 3 [Issue #2262](rzwitserloot/lombok#2262); fixed by github user @Lekanich - thank you!
• BUGFIX: Some of the code generated by @Builder did not include this. prefixes when accessing fields. While semantically it didn't matter, if you use the 'add this prefix for field accesses' save action in eclipse, the save action would break. [Issue #2327](rzwitserloot/lombok#2327)
• BUGFIX: When lombok copies javadoc from fields to relevant methods, it should generate an appropriate @return this line if lombok copies the javadoc to a generated setter that is chainable (returns itself). It didn't do that when generating the 'setters' in a @Builder. Lombok also didn't generate an appropriate @return item for @With methods. The javadoc has also been updated slightly (the this reference in the javadoc is now rendered in a code tag).[Issue #2323](rzwitserloot/lombok#2323)
• IMPROBABLE BREAKING CHANGE: Lombok now generates qualified types (so, Outer.Inner instead of just Inner) in most type signatures that it generates; this should avoid exotic scenarios where the types lombok puts in signatures end up referring to unintended other types, which can occur if your class implements an interface that itself defines a type with the same name as one defined in your source file. I told you it was exotic. Thanks to Hunter Anderson for doing some preliminary work on this change. [Issue #2268](rzwitserloot/lombok#2268)
• IMPROBABLE BREAKING CHANGE: Running java -jar lombok.jar config -v <files> no longer shows which files do not mention the specified keys. Use --non-mentioned or -n to show them anyway.

Changelog

Sourced from lombok's changelog.

v1.18.24 (April 18th, 2022)

• PLATFORM: JDK18 support added. [Issue #3129](projectlombok/lombok#3129).
• PLATFORM: Using ecj and maven? There's now a command line option to integrate lombok into your build chain. [Issue #3143](projectlombok/lombok#3143).
• FEATURE: @ToString has an annotation parameter called onlyExplicitlyIncluded. There's now a config key lombok.toString.onlyExplicitlyIncluded to set this property as well. [Issue #2849](projectlombok/lombok#2849).
• 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. [Issue #2693](projectlombok/lombok#2693) [Pull Request #2996](projectlombok/lombok#2996). Thanks @​YonathanSherwin!
• FEATURE: You can now use @Accessors(makeFinal = true) to make final getters, setters, and with-ers. [Issue #1456](projectlombok/lombok#1456).
• BUGFIX: Various save actions and refactor scripts in eclipse work better. [Issue #2995](projectlombok/lombok#2995) [Issue #1309](projectlombok/lombok#1309) [Issue #2985](projectlombok/lombok#2985) [Issue #2509](projectlombok/lombok#2509).
• BUGFIX: Eclipse projects using the jasperreports-plugin will now compile. [Issue #1036](projectlombok/lombok#1036).
• BUGFIX: inner classes in @UtilityClass classes were broken in JDK9+. [Issue #3097](projectlombok/lombok#3097).
• BUGFIX: Delomboking code with @Builder.Default in it would generate different code vs lombok itself. [Issue #3053](projectlombok/lombok#3053).
• BUGFIX: Combining @NonNullByDefault and lombok.addNullAnnotations would generate two @Nullable annotations and thus generate a compiler error. [Issue #3120](projectlombok/lombok#3120). Thanks @​JohnPaulTaylorII!
• BUGFIX: Null analysis in eclipse was broken for incremental builds. [Issue #3133](projectlombok/lombok#3133).
• BUGFIX VerifyError would show up in the latest eclipse release when using various refactor scripts. [Issue #3134](projectlombok/lombok#3134).
• BUGFIX: The various @Log annotations can now be placed on inner enums and records. [Issue #2990](projectlombok/lombok#2990).
• 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. [Issue #3063](projectlombok/lombok#3063)
• 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](projectlombok/lombok#2904)

v1.18.22 (October 6th, 2021)

• PLATFORM: JDK17 support added. [Issue #2898](projectlombok/lombok#2898).
• FEATURE: Added the @StandardException feature. [Pull Request #2702](projectlombok/lombok#2702).
• IMPROBABLE BREAKING CHANGE: If the underlying compiler and --release / --source option is 10 or higher, lombok's val is now replaced by final var. That means compound declarations such as val x = 10, y = 12; now fail (lombok's old val implementation supported it, javac's var does not), but IDE support in particular is more reliable. We decided it was worth the tradeoff.
• BUGFIX: Syntax highlighting in VSCode now works reliably when using lombok. [Issue #2950](projectlombok/lombok#2950).
• BUGFIX: Eclipse's organize imports feature would sometimes remove your lombok.val import. [Issue #2972](projectlombok/lombok#2972).

v1.18.20 (April 2nd, 2021)

• PLATFORM: JDK16 support added. [Issue #2681](projectlombok/lombok#2681).
• PLATFORM: All lombok features updated to act in a sane fashion with JDK16's record feature. In particular, you can annotate record components with @NonNull to have lombok add null checks to your compact constructor (which will be created if need be).
• BUGFIX: Trying to use a lambda expression as parameter to an @ExtensionMethod did not work. [Issue #2741](projectlombok/lombok#2741). (by @​Rawi01).
• BUGFIX: @SuperBuilder with an existing constructor caused issues in eclipse. [Issue #2704](projectlombok/lombok#2704). (by @​JanRieke).
• BUGFIX: Using @SuperBuilder with a handwritten builder class caused issues. [Issue #2701](projectlombok/lombok#2701). (by @​JanRieke).
• BUGFIX: Lombok interacts properly with the new save actions in eclipse 2021-03.
• POTENTIAL BUGFIX: lombok + errorprone could cause IllegalArgumentException if using the MissingSummary bug pattern. [Issue #2730](projectlombok/lombok#2730).

v1.18.18 (January 28th, 2021)

• BUGFIX: Various tools using ecj under the hood (including intellij) could cause corrupt class files to be generated. [PR #2637](projectlombok/lombok#2637), [lombok-intellij-plugin issue #969](mplushnikov/lombok-intellij-plugin#969).
• BUGFIX: Netbeans would not work with 1.18.16 anymore. [Issue #2612](projectlombok/lombok#2612).
• BUGFIX: @ExtensionMethod support in ecj improved when generics are involved. [Issue #2648](projectlombok/lombok#2648), [PR #2658](projectlombok/lombok#2658) thanks to @​Rawi01.
• PLATFORM: using lombok.config files when compiling with sbt 1.4 now works again. [Issue #2645](projectlombok/lombok#2645)

v1.18.16 (October 15th, 2020)

• BUGFIX: Version 1.18.14 could not be installed in Eclipse, it would break Eclipse.
• BREAKING CHANGE: mapstruct users should now add a dependency to lombok-mapstruct-binding. This solves compiling modules with lombok (and mapstruct).
• IMPROBABLE BREAKING CHANGE: The generated hashcode has changed for classes that include both primitive fields and reference fields.
• FEATURE: Similar to @Builder, you can now configure a @SuperBuilder's 'setter' prefixes via @SuperBuilder(setterPrefix = "set") for example. We still discourage doing this. [Pull Request #2357](projectlombok/lombok#2357).
• FEATURE: If using @Synchronized("lockVar"), if lockVar is referring to a static field, the code lombok generates no longer causes a warning about accessing a static entity incorrectly. [Issue #678](projectlombok/lombok#678)
• FEATURE: @Jacksonized on a @Builder or @SuperBuilder will configure Jackson to use this builder when deserializing. [Pull Request #2387](projectlombok/lombok#2387) thanks to @​JanRieke. @​Jacksonized documentation.
• FEATURE: The checkerframework support has been updated; the relevant annotations were renamed in checkerframework's APIs, lombok now generates the annotations according to their current API names.
• FEATURE: Add option to cache hashCode via @EqualsAndHashCode(cacheStrategy = EqualsAndHashCode.CacheStrategy.LAZY). [Issue #784](projectlombok/lombok#784) [Pull Request #2513](projectlombok/lombok#2513) thanks to @​andrebrait.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)