m2e-code-quality/m2e-code-quality — pull request #13 by anthonydahanne (2012-08-05 02:54:51+00:00)
Title: add new preference page to choose whether or not checkstyle settings should be used to  write formatter/cleanup config when importing projects

Hello,
Currently, the checkstyle m2e connector does not specify any value for the syncFormatter attribute (https://github.com/m2e-code-quality/m2e-code-quality/blob/master/com.basistech.m2e.code.quality.checkstyle/src/main/java/com/basistech/m2e/code/quality/checkstyle/EclipseCheckstyleProjectConfigurator.java#L124 )
so its value is false by default.
To set it to true, we could add :
```java
pcWorkingCopy.setSyncFormatter(true);
```

but the pull request I suggest goes beyond that, allowing the user to decide whether or not (thanks to a new preference page) this value may be set to true when importing projects with a checkstyle configuration in their pom.

This syncformatter attribute, also known as "write formatter/cleanup config (experimental)" (when you right click on a project , checkstyle section) generates JDT formatting rules based on the checkstyle configuration, when enabled.
Bottom line : when importing his maven project, not only the user will have Eclipse enable checkstyle with the right configuration, but also JDT formatter rules matching the checkstyle configuration !