villadotcom.blogg.se - Lombok annotations not working eclipse

Lombok annotations not working eclipse update#
Lombok annotations not working eclipse code#

PR #2637, lombok-intellij-plugin issue #969. BUGFIX: Various tools using ecj under the hood (including intellij) could cause corrupt class files to be generated.POTENTIAL BUGFIX: lombok + errorprone could cause IllegalArgumentException if using the MissingSummary bug pattern.

(by BUGFIX: Lombok interacts properly with the new save actions in eclipse 2021-03. (by BUGFIX: Using with a handwritten builder class caused issues. (by BUGFIX: with an existing constructor caused issues in eclipse.

BUGFIX: Trying to use a lambda expression as parameter to an did not work.

In particular, you can annotate record components with to have lombok add null checks to your compact constructor (which will be created if need be).

PLATFORM: All lombok features updated to act in a sane fashion with JDK16's record feature.

BUGFIX: Eclipse's organize imports feature would sometimes remove your lombok.val import.

BUGFIX: Syntax highlighting in VSCode now works reliably when using lombok.

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.

IMPROBABLE BREAKING CHANGE: If the underlying compiler and -release / -source option is 10 or higher, lombok's val is now replaced by final var.

Lombok will thus copy some of these new annotations e.g.

IMPROBABLE BREAKING CHANGE: Lombok now understands a few more annotations that imply "this field should not ever contain a null reference".

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.

Lombok annotations not working eclipse update#

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 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).BUGFIX: The various annotations can now be placed on inner enums and records.

BUGFIX VerifyError would show up in the latest eclipse release when using various refactor scripts.

Thanks BUGFIX: Null analysis in eclipse was broken for incremental builds.

BUGFIX: Combining and lombok.addNullAnnotations would generate two annotations and thus generate a compiler error.

Lombok annotations not working eclipse code#

BUGFIX: Delomboking code with in it would generate different code vs lombok itself.BUGFIX: inner classes in classes were broken in JDK9+.BUGFIX: Eclipse projects using the jasperreports-plugin will now compile.BUGFIX: Various save actions and refactor scripts in eclipse work better.Thanks FEATURE: You can now use = true) to make final getters, setters, and with-ers. Lombok does getUShape, but if you prefer the getuShape style, add to nfig: = beanspec. FEATURE: Turning a field named uShape into a getter is tricky: getUShape or getuShape? The community is split on which style to use.There's now a config key to set this property as well. FEATURE: has an annotation parameter called onlyExplicitlyIncluded.PLATFORM: Using ecj and maven? There's now a command line option to integrate lombok into your build chain.BUGFIX: Using val together with any call to a method that explicitly resolves to a default impl in an interface didn't work in javac.BUGFIX: Using the refactor script: "Rename field" in a file in eclipse or VSCode would cause issues.BUGFIX: Eclipse didn't find usages of extension methods ( in "find references" nor rename-refactoring.FEATURE: Jakarta has some non-null annotations (such as ) which we now support.BUGFIX: on a primitive array field on a record wouldn't work.BUGFIX: Eclipse 4.27 and VSCode 1.14.0 would ignore nfig.