Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

M2E Development Environment

Revision as of 08:27, 18 December 2013 by Igor.ifedorenko.com (Talk | contribs) (Submitting patches)

M2E
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse Source

Download and unpack Eclipse latest SDK Kepler build from http://download.eclipse.org/eclipse/downloads/ .

Install m2e 1.4 or newer from http://download.eclipse.org/technology/m2e/releases .

Clone m2e-core repository. Committers should use ssh://YOUR_COMMITTERID@git.eclipse.org/gitroot/m2e/m2e-core.git. For read-only access use either git://git.eclipse.org/gitroot/m2e/m2e-core.git or http://git.eclipse.org/gitroot/m2e/m2e-core.git.

Import m2e-core as existing maven project. Follow onscreen instructions, allow m2e to install additional software and restart eclipse when requested.

Clone m2e-core-tests repository. Developers should use git@github.com:tesla/m2e-core-tests.git. See https://github.com/tesla/m2e-core-tests for other ways to clone m2e-core-tests repository.

Import m2e-core-tests as existing maven project.

Submitting patches

m2e team only accepts git-format-patch formatted patches attached to eclipse bugzilla. In most cases the following command generates needed patch format from the most recent commit in the git repository.

   git format-patch -1


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