FindBugs looks at .class files, not source code. The CheckStyle tool or the recently-opensourced CodePro tool could help with this.
+0.2 to spaces (I don't care enough for a full +1). The JDK is a prime example of tabs done wrong. Chris -----Original Message----- From: Wade Chandler [mailto:hwadechandler-apa...@yahoo.com] Sent: Sunday, December 05, 2010 3:31 PM To: river-dev@incubator.apache.org Subject: Re: Formatting of River Source Tree ----- Original Message ---- > From: Patricia Shanahan <p...@acm.org> > To: river-dev@incubator.apache.org > Sent: Sun, December 5, 2010 1:26:04 PM > Subject: Re: Formatting of River Source Tree > > The good news about spaces is that the code will display with reasonable > indentation in *all* environments, including e.g. quotes in e-mail, > regardless of the choice of e-mail client. > Yes, and if it is really too big a deal, then something like findbugs can be used to report issues without failing the build and blame can be used to keeps folks correcting any issues with tabs or space setting differences. In the wiki some minor processes could be defined. A simple page "Working with the sources" with hints should suffice. My opinion anyways. I prefer spaces. Wade ================== Wade Chandler Software Engineer and Developer NetBeans Dream Team Member and Contributor http://wiki.netbeans.org/wiki/view/NetBeansDreamTeam http://www.netbeans.org
