I haven't used Lombok due to similar reasons as Jens described but have had really great success with annotation processing libraries like Immutables ( http://immutables.github.io/), AutoValue, etc. I've even started writing my own annotation processors to help reduce boilerplate.
On Wed, Mar 16, 2016 at 12:37 PM Jens <[email protected]> wrote: > If its just for value classes and factories you better use Google's > AutoValue / AutoFactory projects which are based on annotation processing > instead of hacking the Java compiler as Lombok does. > > Personally I would never use Lombok. As it adds code during compilation, > that code is invisible to tools that work on Java source. IMHO Lombok is > fragile and can break easily with any JDK update, you can also see this in > the changelog as it contains quite some "Bugfix: X breaks starting with JDK > Y". The reason is that Lombok relies on the com.sun.tools.javac package > which is considered a private API. > > So I would generally advice using annotation processors instead. > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
