Skip to main content
Jump to: navigation, search

M2E Development Environment

Revision as of 23:20, 14 January 2014 by (Talk | contribs)

Mailing ListForumsIRCmattermost
OpenHelp WantedBug Day
Browse Source

Download and unpack Eclipse latest SDK Kepler build from .

Install m2e 1.4 or newer from .

Clone m2e-core repository. Committers should use ssh:// For other ways to access m2e git repository, including read-only anonymous access see

Import m2e-core as existing maven project. Follow onscreen instructions, allow m2e to install additional software and restart eclipse when requested. Give Eclipse some time to update project configuration after restart. You may need to do Project/Clean.../Clean_all_projects to clear all compilation errors.

Clone m2e-core-tests repository. Developers should use See for other ways to clone m2e-core-tests repository.

Import m2e-core-tests as existing maven project.

Building m2e on command line

Building m2e on command line is a two step process, both performed from root of m2e-core checkout directory

First, you need to *install* m2e maven runtime to local maven repository

  mvn clean install -f m2e-maven-runtime/pom.xml

Then, package m2e update site

  mvn clean package

The repository is created under directory.

Running m2e automated regression tests on command line

To run m2e automated regression tests, execute the following common from m2e-core-tests checkout directory

  mvn clean integration-test -Puts,its -Dm2e-core.url=file://<full-path-to-m2e-repository>

Submitting patches

m2e only accepts changes contributed via Gerrit. Here is the wiki that explains how to use it . Good luck.

According to eclipse legal poster, all contributors must have signed Eclipse CLA and their bugzilla email and git commit author must match (otherwise Eclipse git server refuses contribution).

Back to the top