Skip to main content
Jump to: navigation, search

M2E Development Environment

Revision as of 23:47, 17 February 2013 by Igor.ifedorenko.com (Talk | contribs)

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

Download and unpack Eclipse latest SDK Juno build from http://download.eclipse.org/eclipse/downloads/ . Both 3.8 and 4.2 builds are expected to work.

Install m2e 1.2 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:sonatype/m2e-core-tests.git. For read-only access use either git://github.com/sonatype/m2e-core-tests.git.

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

In addition to normal description of the change, the commit message must also include a statement that confirms that the contributor

  1. wrote 100% of the code;
  2. that they have the right to contribute the code to Eclipse;
  3. the file header contains the appropriate License

(see eclipse legal poster for reasons why we require this).

Back to the top