Skip to main content
Jump to: navigation, search

Difference between revisions of "M2E Development Environment"

(Replaced content with "[https://www.eclipse.org/m2e/documentation/m2e-development-environment.html This page is now here]")
 
(9 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{M2E}}
+
[https://www.eclipse.org/m2e/documentation/m2e-development-environment.html This page is now here]
 
+
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. 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 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 [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]]
+

Latest revision as of 07:25, 14 November 2014

This page is now here

Back to the top