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.
Difference between revisions of "M2E Development Environment"
(→Submitting patches) |
|||
Line 1: | Line 1: | ||
{{M2E}} | {{M2E}} | ||
− | Download and unpack Eclipse latest SDK Kepler build from http://download.eclipse.org/eclipse/downloads/ . | + | 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 . | 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 | + | Clone m2e-core repository. Committers should use ssh://YOUR_COMMITTERID@git.eclipse.org:29418/m2e/m2e-core. For other ways to access m2e git repository, including read-only anonymous access see https://git.eclipse.org/r/#/admin/projects/m2e/m2e-core |
Import m2e-core as existing maven project. Follow onscreen instructions, allow m2e to install additional software and restart eclipse when requested. | Import m2e-core as existing maven project. Follow onscreen instructions, allow m2e to install additional software and restart eclipse when requested. | ||
Line 15: | Line 15: | ||
== Submitting patches == | == Submitting patches == | ||
− | m2e | + | m2e only accepts changes contributed via Gerrit. Here is the wiki that explains how to use it http://wiki.eclipse.org/Gerrit . Good luck. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
According to [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf 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). | According to [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf 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). | ||
[[Category:M2E]] | [[Category:M2E]] |
Revision as of 22:52, 14 January 2014
M2E | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug 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:29418/m2e/m2e-core. For other ways to access m2e git repository, including read-only anonymous access see https://git.eclipse.org/r/#/admin/projects/m2e/m2e-core
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 only accepts changes contributed via Gerrit. Here is the wiki that explains how to use it http://wiki.eclipse.org/Gerrit . 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).