lombok | Very spicy additions to the Java programming language

This is not possible because maven-compiler-plugin does not currently follow dependencyManagement rules (MCOMPILER-391, go vote for it!).

The only thing you can do for now it seems is to declare a lombok.version property in the parent pom, and use that in your annotationProcessorPath declaration.

(note that Spring Boot already defines such a property for Lombok)

You are running the project via Java 1.8 and add the --add-opens option to the runner. However Java 1.8 does not support it.

So, the first option is to use Java 11 to run the project, as Java 11 can recognize this VM option.

Another solution is to find a place where --add-opens is added and remove it. Check Run configuration in IntelliJ IDEA (VM options field) and Maven/Gradle configuration files for argLine (Maven) and jvmArgs (Gradle)

Vaadin 23:

In Vaadin 23 there is now a new feature, which allows you to define executor for DataCommunicator to use for asynchronous operation with Grid. If the value is null, DataCommunicator will operate synchronously and this is the default. If executor is defined, the fetch callback is run by executor and Grid is updated using ui.access(..). This requires Push to be enabled.

grid.getDataCommunicator().enablePushUpdates(Executors.newCachedThreadPool());

Vaadin 14:

One can attempt to reduce query time with caches. You can either use some generic cache like ehcache, or integrate cache in your data provider. It is application specific which is better for you, global or local cache.

If the query is still taking that long, then I would propose alternative approach for your UI. Instead of using callback data provider, use Grid with in memory data provider, but do not load whole data to the data provider at once. Instead create a paged view. Query new data when user clicks e.g. "next"/"previous", etc. buttons. And update the UI using UI#access method async when query completes.

How to fix it:

• go to https://plugins.jetbrains.com/plugin/6317-lombok/versions
• download .zip with the latest version (0.34.1-2019.1)
• unpack it to ~/android-studio/plugins (use your path to Android Studio)
• restart IDE

not a resolution but there is a (working) workaround in the comments of the issue on github.

@SuperBuilder(toBuilder=true) supports generic classes and refining the type parameter from the superclass in the subclass. So your classes and their annotations are fine.

However, lombok sometimes has problems inferring the correct type for val, especially when type parameters are involved.

The solution is to replace val with the actual type PointsExpirationByEarnedDatePolicyBuilder.

This failure is likely due to an issue between java 17 and older lombok versions. Building with java 17.0.1, lombok 1.18.20 and maven 3.8.1 caused a vague "Compilation failure" for me as well. I upgraded to maven 3.8.3 which also failed but provided this detail on the failure:

java.lang.NullPointerException: Cannot read field "bindingsWhenTrue" because "currentBindings" is null

Searching for this failure message I found this issue on stackoverflow leading me to a bug in lombok. I upgraded to lombok 1.18.22 and that fixed the compilation failure for a successful build.

According to this records are supported from Lombok version v1.18.20

@Builder on records is supported since the last release v1.18.20. Which version are you using? Note that this may also be just an IDE issue. If you are using IntelliJ, it may not be supported, yet.

Probably an IntelliJ issue ... try writing the code without IntelliJ auto-complete, see if it compiles ... if it does ... its an IntelliJ issue ... if it does not, something is wrong with your code.

I always use @RequiredArgsContstructor and it generates autowired constructor. In this case @Autowired annotation isn't needed.

Constructor Injection in Spring with Lombok.