Skip to content
A collection of Eclipse plugins for M2Eclipse that carry configuration from the Checkstyle, FindBugs and PMD Maven plugins to their corresponding Eclipse plugins.
Latest commit a093d82 May 22, 2016 @ArloL ArloL Add check for empty result
Failed to load latest commit information.
com.basistech.m2e.code.quality.checkstyle.feature Revert change of update site URL Jan 12, 2015
com.basistech.m2e.code.quality.checkstyle.test Add test for pattern conversion Feb 26, 2016
com.basistech.m2e.code.quality.checkstyle Remove unnecessary javadoc May 10, 2016
com.basistech.m2e.code.quality.findbugs.feature Revert change of update site URL Jan 12, 2015
com.basistech.m2e.code.quality.findbugs.test Make all local variables and parameters final where possible Feb 26, 2016
com.basistech.m2e.code.quality.findbugs Consistently indent throws declarations Feb 27, 2016
com.basistech.m2e.code.quality.pmd.feature Revert change of update site URL Jan 12, 2015
com.basistech.m2e.code.quality.pmd Use isEmpty instead of size Feb 27, 2016
com.basistech.m2e.code.quality.shared Add check for empty result May 22, 2016 Revert "Change packaging to eclipse-repository" Jan 12, 2015
doc update release doc.: Nov 5, 2012
luna Use latest checkstyle and version specific update site Feb 7, 2016
mars Use version specific update site instead of composite site Apr 22, 2016
test-projects Add checkstyle-8 demo project May 10, 2016
tools Try to find the eclipse location on MacOS X Jan 8, 2015
.gitignore Ignore the findbugs.p2 repository in git Jan 8, 2015
.hgignore - Initial import of first release Feb 28, 2010
.travis.yml Use new travis container based architecture Dec 26, 2014 Create Jan 8, 2015 Change eclipse product Apr 24, 2016
m2e-code-quality.setup Add logback to oomph setup Feb 26, 2016
pom.xml maven-jarsigner-plugin:1.3.2 -> 1.4 Feb 27, 2016


This project provides Eclipse plugins that bridge the Maven and Eclipse plugins for Checkstyle and PMD. In a Maven project that uses Checkstyle or PMD, the project configures the tools via configuration information the POM or pointed to by the POM.

On the other hand, the Eclipse plugins for these tools provide annotations and as-you-edit notifications of issues. Thus, it's desirable to turn the Maven plugins off in M2E, to turn the Eclipse plugins on, and to move configuration from the Maven plugins to the Eclipse plugins.

In a perfect world, there would be some sort of standardized API that would allow a build tool like Maven to publish this configuration and for IDE plugins to consume it. In reality, this has to be arranged, one plugin-pair at a time, and depends rather delicately on the OSGi manifests of the receiving plugins. If they don't export enough API for programmatic configuration, it cannot be done.

These Eclipse plugins are built with the Tycho Maven plugin. The marriage of OSGi, Eclipse, and Maven is imperfect. In particular, it rarely works to run a build that does not start with 'clean'.

This project has Oomph, and you can set up an Eclipse development workspace of it in one click by:

  1. Downloading the Eclipse Installer from and starting it.
  2. On the initial page, click on the Switch to advanced mode button in the top right.
  3. On the Product page, select Eclipse for RCP and RAP Developers.
  4. On the Projects page, collapse the Eclipse Projects to scroll down to the Github Projects and select m2e-code-quality.
  5. Choose your preferred installation settings on the Variables page.
  6. Finish the wizard and watch how your development environment is being assembled, courtesy of Oomph.

See doc/ for information about how all of this is released.

Activity here is 'coordinated' on a mailing list:

Something went wrong with that request. Please try again.