Update dependency org.projectlombok:lombok to v1.18.24

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.projectlombok:lombok (source)	1.16.10 -> 1.18.24

---

Release Notes

projectlombok/lombok

v1.18.24

Compare Source

v1.18.22

Compare Source

v1.18.20

Compare Source

v1.18.18

Compare Source

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.
• 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
• FEATURE: @Jacksonized on a @Builder or @SuperBuilder will configure Jackson to use this builder when deserializing. Pull Request #​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
• 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, Issue #​1543
• BUGFIX: Delombok prints the first this parameter. Issue #​2444
• BUGFIX: Using val in combination with values whose generics include wildcards that reference themselves would cause a StackOverflowError in javac. Issue #​2358.
• BUGFIX: Using @SuperBuilder on a class that has some fairly convoluted generics usage would fail with 'Wrong number of type arguments'. Issue #​2359 Pull Request #​2362
• BUGFIX: Various lombok annotations on classes nested inside enums or interfaces would cause errors in eclipse. Issue #​2369
• BUGFIX: Trying to add @ExtensionMethods with exactly 2 arguments would fail in eclipse. Issue #​1441 Pull Request #​2376 thanks to @​Rawi01.
• BUGFIX: Javac sets incorrect annotated type on with methods. Issue #​2463

v1.18.14

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

v1.18.12

Compare Source

• 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, Issue #​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. 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
• 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
• 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
• 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; 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
• 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
• 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
• 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.

v1.18.10

Compare Source

v1.18.8

Compare Source

v1.18.6

Compare Source

v1.18.4

Compare Source

v1.18.2

Compare Source

v1.18.0

Compare Source

v1.16.22

Compare Source

v1.16.20

Compare Source

v1.16.18

Compare Source

v1.16.16

Compare Source

v1.16.14

Compare Source

v1.16.12

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.