Closed larsgrefer closed 5 years ago
I am actually not the biggest fan of lombok and this project the fields are not changing very often such that i do not see the benefit compared to the tradeoffs.
Are you fine with this @larsgrefer?
As you like it. This was just a suggestions.
But I'm curious: What are the tradeoffs you're talking about?
Here are my tradeoffs. Disclaimer: Maybe they are outdated and if so, please tell me ;-)
Development:
Environment:
Also interesting is this blogpost: https://medium.com/@vgonzalo/dont-use-lombok-672418daa819. It has some interesting points...
By the way, another approach is https://immutables.github.io/
I'm using IntelliJ IDEA as IDE and have absolutely no problems with refactoring/renamings or IDE support in general. It's all handled transparently.
JaCoCo intentionally ignores all the code generated by Lombok.
The Gradle Plugin I've used here (io.freefair.lombok
) also reconfigures the javadoc
Task in order to use the delomboked-sources.
Coverage decreased (-1.4%) to 84.746% when pulling 536aff5d83af71903a38831790a44defc5cb798b on larsgrefer:feature/lombok into c6eec4917605a91edab1a425696631a7db435a9e on aaschmid:master.