A collection of Eclipse plugins for M2Eclipse that carry configuration from the Checkstyle, FindBugs and PMD Maven plugins to their corresponding Eclipse plugins.
Branch: develop
Clone or download
Bananeweizen and vorburger Fix #203: Have org.apache.commons.lang in targets
The POM repositories and the Eclipse targets are somewhat out of sync.
As a quickfix just add the missing bundle to the Eclipse target. In the
long run I suggest to use a .target file in the Maven build, too,
instead of fetching whatever is available on the repository URLs.
Latest commit 2cc383b Feb 7, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
com.basistech.m2e.code.quality.checkstyle.feature Next version: 1.1.3-SNAPSHOT Dec 19, 2018
com.basistech.m2e.code.quality.checkstyle.test Add Automatic-Module-Name header Feb 6, 2019
com.basistech.m2e.code.quality.checkstyle fix/suppress some compiler warnings Feb 7, 2019
com.basistech.m2e.code.quality.findbugs.feature Use uppercase B in SpotBugs/FindBugs Feb 6, 2019
com.basistech.m2e.code.quality.findbugs.test Use uppercase B in SpotBugs/FindBugs Feb 6, 2019
com.basistech.m2e.code.quality.findbugs Use uppercase B in SpotBugs/FindBugs Feb 6, 2019
com.basistech.m2e.code.quality.pmd.feature Next version: 1.1.3-SNAPSHOT Dec 19, 2018
com.basistech.m2e.code.quality.pmd.test Removed EclipseConfigManager and reuse at ProjectConfigurator level Nov 5, 2018
com.basistech.m2e.code.quality.pmd fix/suppress some compiler warnings Feb 7, 2019
com.basistech.m2e.code.quality.shared.test Add Automatic-Module-Name header Feb 6, 2019
com.basistech.m2e.code.quality.shared fix/suppress some compiler warnings Feb 7, 2019
com.basistech.m2e.code.quality.site Bump repository-utils from 1.1.0 to 1.3.0 Jan 23, 2019
com.basistech.m2e.code.quality.spotbugs.feature Use uppercase B in SpotBugs/FindBugs Feb 6, 2019
com.basistech.m2e.code.quality.spotbugs.test Add Automatic-Module-Name header Feb 6, 2019
com.basistech.m2e.code.quality.spotbugs Use uppercase B in SpotBugs/FindBugs Feb 6, 2019
doc Fix typos Feb 7, 2019
mars Fix #203: Have org.apache.commons.lang in targets Feb 7, 2019
neon Fix #203: Have org.apache.commons.lang in targets Feb 7, 2019
oxygen Fix #203: Have org.apache.commons.lang in targets Feb 7, 2019
photon Fix #203: Have org.apache.commons.lang in targets Feb 7, 2019
test-projects Add test project for #178 Dec 12, 2018
tools Do not include unreleased changed Dec 21, 2018
.editorconfig Use EditorConfig to standardize formatting (#165) Oct 4, 2018
.gitignore Enable incremental deploy Nov 10, 2018
.hgignore - Initial import of first release Feb 28, 2010
.travis.yml Automatic changelog Dec 3, 2018
CHANGELOG.md Release 1.1.2.201812191233-r [skip ci] Dec 19, 2018
CONTRIBUTING.md Create CONTRIBUTING.md Jan 8, 2015
LICENSE add missing /LICENSE (ASL) file (#148) Sep 19, 2018
README.md Fix typos Feb 7, 2019
m2e-code-quality.setup Add newer eclipse versions to oomph Dec 3, 2018
pom.xml Bump spotbugs-maven-plugin from 3.1.10 to 3.1.11 Feb 4, 2019

README.md

m2e-code-quality Build Status

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

Installation

The latest release can be installed from the Eclipse Update Site at https://m2e-code-quality.github.io/m2e-code-quality-p2-site/

Development environment

This project uses Oomph, and you can set up an Eclipse development environment with the following steps:

  1. Make sure your JRE/JDK has the JCE installed (See http://stackoverflow.com/questions/42128981/eclipse-pmd-plug-in-handshake-failure and https://github.com/pmd/pmd-eclipse-plugin/issues/19)
  2. Downloading the Eclipse Installer from https://www.eclipse.org/downloads/ and start it.
  3. On the initial page, click on the Switch to advanced mode button in the top right.
  4. On the Product page, select Eclipse for RCP and RAP Developers.
  5. On the Projects page, collapse the Eclipse Projects to scroll down to the GitHub Projects and select m2e-code-quality.
  6. Make sure to choose the HTTPS anonymous option for the repository.
  7. Choose other preferred installation settings on the Variables page.
  8. Finish the wizard and watch your development environment being assembled.
  9. Create an Eclipse run configuration. The target platform will automatically be setup correctly.

Release

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

Mailing list

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