Answers to: Apply lombok for Ivy project

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Fri, 06 Dec 2019 11:15:36 -0500

Hi @TareqK no unfortunately this issue got no priority on the roadmap so there is still no native support for it. What can work for some cases where annotation magic is required:

use share-engine-core-classpath to get a valid classpath for ivy.core deps
compile with a classic maven-compiler-plugin and its associated stack (using the classpath property)

But I'd only do this in an isolated base project with a specific scope. Since ivy compile functionality will be missing...

Comment by TareqK on Reguel Wermelinger's answer

TareqK — Fri, 06 Dec 2019 03:08:27 -0500

Is there any update on this? Do annotation processors work out of the box for newer platforms (7.0+)?

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Fri, 13 Oct 2017 04:37:43 -0400

The idea was to make options from the JDT compiler, such as annotationProcessing, available for users of the project-build-plugin. The driver for it was lombok. But as lombok annotation processing did not solve the lombok build issues when using the project-build-plugin, we also did not invent these options as part of the project-build-plugin compile goals. Still I can imagine other scenarios where an annotationProcessing option would be required. But I didn't want to support it while there is no real project that really uses the feature.

Comment by Hap Em on Reguel Wermelinger's answer

Hap Em — Fri, 13 Oct 2017 04:15:59 -0400

Hello Reguel,

In the XIVY-1606, I saw you have the patch "lombokOptions.patch" --> As i understand, the change code is using for annotationProcessors (especially, lombok project).

What is the status of this code? is it merged to new ivy version?

Thanks! Hap Em,

Answer by Reguel Wermelinger

Reguel Wermelinger — Wed, 11 Oct 2017 06:40:05 -0400

What I know is that from the ivy.core there has been some investigation in making the project-build-plugin able to compile with lombok. https://jira.axonivy.com/jira/browse/XIVY-1606 But that approach failed. Roughly concluded lombok is very cool for the user, but the integration into eclipse and other tools has been done very dirty. And its not easy to apply them anywhere else...

In my opinion there is also no big need to use lombok in ivy projects. Yes you have some extra features such as builders for your pojos. But we already provide a simple way to define POJOs via DataClasses. As with lombok you have an easy Editor to define classes and its properties. And you have the same drawbacks such as very weak refactoring support...