For that reason, checkstyle goal should run before the execution of eclipse:eclipse.

In the above snippet, you might noticed that Eclipse will look for the target/checkstyle-checker.xml file which is created by maven-checkstyle-plugin when checkstyle goal runs. This file is located in build-tools as well and contains the information needed by Eclipse to setup Checkstyle. This will require to setup maven-eclipse-plugin e.g. The second step is to let Eclipse know about your Checkstyle configuration. You may run mvn checkstyle:checkstyle to perform a Checkstyle analysis, and generate a report on violations. Maven-wise your Checkstyle setup is ready. Then you add it as a dependency to maven-checkstyle-plugin e.g. You should create a separate host project for the shared Checkstyle configuration. The first step is to share Checkstyle configuration among the sub-modules. If this is what you are searching for then stay tuned.

With the migration to maven the project was split into many sub-modules and a single Checkstyle configuration consisting of: config, header and suppressions files.

Also, this setup was working fine in Eclipse without particular manual effort. It used to be a single ant-build project with Checkstyle setup. Recently, I had the opportunity to help with the maven-ization of gwt-platform. Have you ever tried to setup your multi-module Maven project with a shared checkstyle configuration and connect it to your eclipse IDE? If you have, I am sure you ‘d agree that it was not as trivial as it should be…

Eclipse how to install checkstyle