chore: Make it possible to use Lombok in Kotlin code

[sgcr]

1. changes proposed in this pull request:
   Make it possible to use Lombok in Kotlin code.

2. src/main/resources/release_notes.md ...

• does not require update

[wsbrenk]

There are 2 not-so-important points that bother me about the Lombok issue:

1. That we include additional packages that could lead to vulnerability problems
2. That its use could result in widespread changes in our source code, making it incredibly difficult for git to produce sane automatic merges without accidents.

Regarding the aspect of Java versus Kotlin, I am very interested in how we can find a way to an Android release, as more and more users are asking for such support. At the moment, apart from this idea, there is neither a concrete roadmap nor a driver.

As I understand, your proposed changes are especially for kotlin code to make the java lomboks usable. As far as we are using lombok, i will accept their usage.

[tychobrailleur]

1. That we include additional packages that could lead to vulnerability problems
2. That its use could result in widespread changes in our source code, making it incredibly difficult for git to produce sane automatic merges without accidents.

As well as polluting git history with a significant number of changes that are only cosmetic in nature. At this point, I feel there is no point in me arguing, so be it.

[wsbrenk]

I really have to say that I am still not a fan of using Lombok. In my opinion, it doesn't make the code any clearer and currently causes a flood of analyzer warnings in IntelliJ, which makes reviewing quite inconvenient.

[sgcr]

I really have to say that I am still not a fan of using Lombok. In my opinion, it doesn't make the code any clearer and currently causes a flood of analyzer warnings in IntelliJ, which makes reviewing quite inconvenient.

Which analyzer warnings do you mean?

From experience, a “flood” of Lombok-related warnings in IntelliJ is often caused by setup or inspection configuration rather than the code itself. If annotation processing (or Lombok support) isn’t enabled in IntelliJ, the IDE may not recognize the generated methods (getters/setters/builders/constructors), which then cascades into lots of false positives (e.g., “cannot resolve method”, “field is never used”, etc.).

Please check these two points:

1. Enable Annotation Processing
   Settings → Build, Execution, Deployment → Compiler → Annotation Processors → “Enable annotation processing”

2. Lombok support / plugin (depending on IntelliJ version)
   Make sure Lombok support is enabled/installed so IntelliJ can interpret the generated code properly.