Format code automatically during compile using google-java-format

There's lot of inconsistent uses of tabs vs spaces throughout the project, and
this is leading to some weird diffs. I submit the project should just enforce
formatting during compile time and just remove any doubt. This way contributors
won't need to update their Eclipse configuration to match, as long as they run
mvn compile, it'll format correctly.

Author: timcharper

pom.xml

@@ -116,6 +116,18 @@
 
 	<build>
 		<plugins>
+			<plugin>
+				<groupId>com.coveo</groupId>
+				<artifactId>fmt-maven-plugin</artifactId>
+				<version>2.6.0</version>
+				<executions>
+					<execution>
+						<goals>
+							<goal>format</goal>
+						</goals>
+					</execution>
+				</executions>
+			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-compiler-plugin</artifactId>
@@ -272,19 +284,19 @@
 		<profile>
 			<id>ossrh</id>
 			<properties>
-          <gpg.executable>gpg</gpg.executable>
-          <gpg.keyname>${env.GPG_KEYNAME}</gpg.keyname>
-          <gpg.passphrase>${env.GPG_PASSPHRASE}</gpg.passphrase>
-          <gpg.defaultKeyring>false</gpg.defaultKeyring>
-          <gpg.publicKeyring>deploy/pubring.gpg</gpg.publicKeyring>
-          <gpg.secretKeyring>deploy/secring.gpg</gpg.secretKeyring>
-      </properties>
+					<gpg.executable>gpg</gpg.executable>
+					<gpg.keyname>${env.GPG_KEYNAME}</gpg.keyname>
+					<gpg.passphrase>${env.GPG_PASSPHRASE}</gpg.passphrase>
+					<gpg.defaultKeyring>false</gpg.defaultKeyring>
+					<gpg.publicKeyring>deploy/pubring.gpg</gpg.publicKeyring>
+					<gpg.secretKeyring>deploy/secring.gpg</gpg.secretKeyring>
+			</properties>
 			<activation>
-          <property>
-              <name>performRelease</name>
-              <value>true</value>
-          </property>
-      </activation>
+					<property>
+							<name>performRelease</name>
+							<value>true</value>
+					</property>
+			</activation>
 			<build>
 				<plugins>
 					<plugin>