In order to get consistent formatting to your projects you need to configure the tools to do it automatically. I would suggest the following:
Eclipse Formatter
For Eclipse there is an option in Preferences (Java->Code Style->Formatter) where you can configure how you want your projects to be formatted. Create a new profile and put your configuration there.
Once you finish, there is an export function (it is well hidden, click on Edit and then Export). Pass the configuration to the rest of the team so that the can import it.
Eclipse Save Actions
Still having the formatter configured does not guaranty you that the developers will format the code before committing so you need to configure automatic format.
Go to the Preferences again (Java->Editor->Save Actions) and select Format Source Code. This way the code is formatted while saving the file.
Eclipse Checkstyle Plugin
Some developers may forget to do these steps correctly, so you need a way to locate that.
Install the Checkstyle plugin for Eclipse:
Once you install the plugin, you can create a configuration for it. The configuration can then be exported for the rest of the team, or even better uploaded to a server and reference to the configuration remotely.
The advantage of having a remote configuration is that you can also reference to it by the maven-checkstyle-plugin and it can give you reports by launching it on a CI server.
If you want to be hard-core you can set the basic configuration (the ones done automatically by the formatter) to errors instead of warnings so that the developer with a misconfigured eclipse sees the error before commiting.
Pre-configured Eclipse
If you want to go to the next level, you create a pre-configured eclipse, and distribute that version to your developers so that they don't need to do anything.
Side-effect bonus: you keep out the version inconsistencies on the development platform. Configuration Management is not about only to the source code, but the development tools also. Keeps things more predictable.