Set a coding standard (sun + 2 space indents is common), then use checkstyle to complain when things don't match. It helps when you can provide IDE formatting configurations that match your chosen coding standard.
Some of the bigger projects use a jenkins precommit bot that checks (among other things) that the checkstyle violations don't go up with a proposed patch. The bot comments on the jira and the committers decide if any violations need to get fixed. Personally, I like this approach better than e.g. trying to fail the build with checkstyle because it allows incremental improvement. On Tue, Mar 17, 2015 at 1:02 PM, Joe Witt <[email protected]> wrote: > Folks, > > It was brought up to me by a contributor the other day that our lack > of consistent formatting makes reviewing true changes difficult. I > see it myself quite often. There are difference between formatting in > Eclipse/Netbeans/manual VI/etc.. > > I am assuming there are good plugins to just automate this sort of > stuff. What do you all think as a good way to go about this? > > Thanks > Joe > -- Sean
