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. http://m2e-code-quality.github.io/m2e-code-quality
Java
Latest commit 8fc5a78 @ArloL ArloL Update sequenceNumber
Failed to load latest commit information.
com.basistech.m2e.code.quality.checkstyle.feature Revert change of update site URL
com.basistech.m2e.code.quality.checkstyle.test Set Execution environment for test projects to JavaSE-1.7
com.basistech.m2e.code.quality.checkstyle Add import for org.apache.commons.lang to use StringEscapeUtils
com.basistech.m2e.code.quality.findbugs.feature Revert change of update site URL
com.basistech.m2e.code.quality.findbugs.test Set Execution environment for test projects to JavaSE-1.7
com.basistech.m2e.code.quality.findbugs Disable adding FindBugs nature when the project type is not Java
com.basistech.m2e.code.quality.pmd.feature Revert change of update site URL
com.basistech.m2e.code.quality.pmd Revert removal of MavenSession for ClassRealm resolution
com.basistech.m2e.code.quality.shared Revert removal of MavenSession for ClassRealm resolution
com.basistech.m2e.code.quality.site Revert "Change packaging to eclipse-repository"
doc update release doc.:
luna Use latest checkstyle and version specific update site
mars Update sequenceNumber
test-projects Update maven checkstyle plugin and organize poms
tools Try to find the eclipse location on MacOS X
.gitignore Ignore the findbugs.p2 repository in git
.hgignore - Initial import of first release
.travis.yml Use new travis container based architecture
CONTRIBUTING.md Create CONTRIBUTING.md
README.md Add readme.
m2e-code-quality.setup Add oomph setup
pom.xml Formatting

README.md

m2e-code-quality

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'.

See docs/release.md for information about how all of this is released.

Activity here is 'coordinated' on a mailing list: m2e-code-quality@googlegroups.com.

Something went wrong with that request. Please try again.