I always use Checkstyle in my projects. I don't believe in the true sense of http://checkstyle.sourceforge.net/config_design.html#VisibilityModifier so I always allow protected and package-private. The only problem I really run into is when I have really long method signatures in my JSNI and it triggers my line length check.
Also, I am not sure I agree with leaving off generics on collections or anything else that's used for GWT RPC serialization (if that's what you meant). Type erasure should make it irrelevant. On Apr 9, 12:59 pm, Eric <erjab...@gmail.com> wrote: > Has anyone configured any of the extant auditing tools for a GWT 2.0.3 > project? For example, most tools declare the use of non-private non- > static instance variables to be errors, but @UiField instance > variables may not be private. Most tools mark declarations of concrete > collections as bad, but one should not use Map<K,V> or List<E> in GWT- > serializable code. > > I would appreciate hearing from any of you who have configured > Checkstyle, PMD, Findbugs, or even static ApectJ @DeclareWarning > aspects for auditing GWT projects. > > Respectfully, > Eric Jablow -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
