如果你不知道，Project Lombok帮助解决了Java的一些麻烦，比如用注释生成getter和setter，甚至是简单的JavaBean，比如用@Data生成。它真的可以帮助我，特别是在50个不同的事件对象中，你有多达7个不同的字段需要用getter来构造和隐藏。我可以用这个删除几乎一千行代码。
然而，我担心从长远来看，这将是一个后悔的决定。当我提到它的时候，火焰战争就会在##Java Freenode频道爆发，提供代码片段会让可能的助手感到困惑，人们会抱怨缺少JavaDoc，而未来的提交者可能无论如何都会删除它。我很享受积极的一面，但我担心消极的一面。
那么:在任何项目中使用Lombok安全吗?积极的影响抵得上消极的影响吗?
当前回答
继续使用Lombok吧，如果有必要，您可以在之后“delombok”您的代码http://projectlombok.org/features/delombok.html
其他回答
我对Lombok的看法是，它只是为编写样板Java代码提供了快捷方式。 当涉及到使用快捷方式来编写Java代码时，我会依赖IDE提供的这些特性——就像在Eclipse中一样，我们可以转到Source > Generate Getters and Setters菜单来生成getter和setter。 我不会依赖Lombok这样的库:
It pollutes your code with an indirection layer of alternative syntax (read @Getter, @Setter, etc. annotations). Rather than learning an alternative syntax for Java, I would switch to any other language that natively provides Lombok like syntax. Lombok requires the use of a Lombok supported IDE to work with your code. This dependency introduces a considerable risk for any non-trivial project. Does the open source Lombok project have enough resources to keep providing support for different versions of a wide range of Java IDE's available? Does the open source Lombok project have enough resources to keep providing support for newer versions of Java that will be coming in future? I also feel nervous that Lombok may introduce compatibility issues with widely used frameworks/libraries (like Spring, Hibernate, Jackson, JUnit, Mockito) that work with your byte code at runtime.
总而言之，我不喜欢用龙目岛来“调味”我的爪哇。
龙目岛很棒，但是……
Lombok打破了注释处理的规则，因为它不生成新的源文件。这意味着它不能与其他注释处理器一起使用，如果它们期望getter /setter或其他任何存在的东西。
Annotation processing runs in a series of rounds. In each round, each one gets a turn to run. If any new java files are found after the round is completed, another round begins. In this way, the order of annotation processors doesn't matter if they only generate new files. Since lombok doesn't generate any new files, no new rounds are started so some AP that relies on lombok code don't run as expected. This was a huge source of pain for me while using mapstruct, and delombok-ing isn't a useful option since it destroys your line numbers in logs.
我最终破解了一个构建脚本，可以同时使用lombok和mapstruct。但我想放弃龙目岛，因为它太粗糙了——至少在这个项目中是这样。我一直在用龙目岛做其他东西。 更新到mapstruct+lombok:这两个库现在可以开箱即用。不过，对于其他注释处理器来说，这个问题仍然存在。
还有长期维护的风险。首先，我建议你阅读一下Lombok的实际工作原理，比如这里有一些来自开发人员的回答。
官方网站还列出了一些缺点，包括Reinier Zwitserloot的这句话:
It's a total hack. Using non-public API. Presumptuous casting (knowing that an annotation processor running in javac will get an instance of JavacAnnotationProcessor, which is the internal implementation of AnnotationProcessor (an interface), which so happens to have a couple of extra methods that are used to get at the live AST). On eclipse, it's arguably worse (and yet more robust) - a java agent is used to inject code into the eclipse grammar and parser class, which is of course entirely non-public API and totally off limits. If you could do what lombok does with standard API, I would have done it that way, but you can't. Still, for what its worth, I developed the eclipse plugin for eclipse v3.5 running on java 1.6, and without making any changes it worked on eclipse v3.4 running on java 1.5 as well, so it's not completely fragile.
总之，虽然Lombok可以节省一些开发时间，但如果有一个不向后兼容的javac更新(例如漏洞缓解)，Lombok可能会让您陷入旧版本的Java，而开发人员则会争先恐后地更新他们对那些内部api的使用。这是否是一个严重的风险显然取决于项目。
我遇到了Lombok和Jackson CSV的问题，当我将我的对象(java bean)编组到CSV文件时，其中的列重复，然后我删除了Lombok的@Data注释，编组工作正常。
我知道我迟到了，但我无法抗拒诱惑:喜欢Lombok的人也应该看看Scala。您在Lombok中发现的许多好想法都是Scala语言的一部分。
关于您的问题:让开发人员尝试Lombok肯定比尝试Scala更容易。试一试，如果他们喜欢，那就试试Scala。
免责声明:我也喜欢Java !
