FWIW, while I'm against Lombok because as others already said it's really hackish and fragile (see also https://groups.google.com/d/topic/bazel-discuss/ZRWdqJfYEPw/discussion, Bazel uses Error Prone <http://errorprone.info> as the Java compiler, which is more-or-less a "fork" of the OpenJDK compiler), we've been using Lombok on a GWT project (setup years ago, in "maintenance mode" nowadays, never bother removing Lombok from the equation). In that project, we've been using "delombok" to generate Java sources that can be used by GWT. But my advice really is to avoid Lombok (JackDaw looks great; but your IDE is capable of generating almost all of what Lombok does, and for immutable value-objects I just use Auto Value from Google, or Immutables.Org)
On Wednesday, March 16, 2016 at 12:29:02 PM UTC+1, Stefan Falk wrote: > > HI! > > I recently stepped over Lombok [1],[2] and saw that it can be used with > GWT. Did anybody of you guys ever use it with GWT? > > Does it pay off or is it unnecessary? > > BR; Stefan > > > [1] https://projectlombok.org/index.html > [2] https://github.com/rzwitserloot/lombok > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
