m2eclipse offers the projectConfigurator extension point to support integration between Maven and Eclipse plugins. But not many Eclipse plugins make use of it yet. Neither the PMD Eclipse plugin nor the Checkstyle Eclipse plugin integrate as project configurator with m2eclipse. That’s why third party plugins like m2e-extensions and m2e-code-quality were developed. This is the second post of a three part article. In the first post, I pointed out how seamless integration of Maven and Eclipse significantly contributes to code quality.[1] Here, I will describe what m2e-extensions and m2e-code-quality offer and why they were not my choice. Finally, in post three, I will share my current best practice for the project configuration - taking account of the requirements in enterprise software development.[2]
Wednesday, February 16, 2011
Wednesday, February 9, 2011
Use Maven to Configure Checkstyle, PMD and FindBugs Consistently in Eclipse
Fail early! That's the best way to minimize development effort. To achieve this, every developer in a project should use the same build configuration as the continous integration server. His local build should use identical settings and should mandatorily execute unit tests and static code analysis. The rulesets for Checkstyle, PMD and FindBugs should automatically be the same under Maven on the command line and under Eclipse. But the problem is: Eclipse, m2eclipse, Maven and the plugins are still on their way towards a seamless integration. This is this first post of a three part article. It describes the overall setup and the official approach using a project configurator. In the second post, I will point out how third party plugins step into the breach, but why they were not my choice.[1] Finally, in post three, I will share my current best practice for the configuration - taking account of the requirements in enterprise software development.[2]
Subscribe to:
Posts (Atom)