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"
| Line 1: | Line 1: | ||
{{M2E}} | {{M2E}} | ||
| − | Download and unpack Eclipse latest SDK | + | Download and unpack Eclipse latest SDK Kepler build from http://download.eclipse.org/eclipse/downloads/ . |
| − | Install m2e 1. | + | 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. | 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. | ||
| Line 9: | Line 9: | ||
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. | ||
| − | Clone m2e-core-tests repository. Developers should use git@github.com: | + | 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. | Import m2e-core-tests as existing maven project. | ||
Revision as of 11:58, 22 August 2013
| 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/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
In addition to normal description of the change, the commit message must also include a statement that confirms that the contributor
- wrote 100% of the code;
- that they have the right to contribute the code to Eclipse;
- the file header contains the appropriate License
(see eclipse legal poster for reasons why we require this).