|information is not applicable to m2e 1.1 and newer|
m2e 1.1 development environment setup is documented in http://wiki.eclipse.org/M2E_Development_Environment
- JDK 1.5 or better
- eclipse + m2e 1.0 + m2e-tycho + m2e-modello + m2e-plexus (see below)
|git repository||groupId||p2 repository||comments|
More information about Eclipse GIT support http://wiki.eclipse.org/Git
All repositories are currently hosted at github
|git repository||groupId||p2 repository||comments|
|m2e-core-tests||org.eclipse.m2e||m2e-core unit and integration tests|
|m2eclipse-tycho||org.sonatype.tycho.m2e||m2eclipse-tycho||tycho and bundle-plugin support|
|m2eclipse-cvs||org.maven.ide.eclipse.cvs||m2eclipse-cvs||No CI build until needed|
|m2eclipse-mavenscm||org.maven.ide.eclipse.mavenscm||m2eclipse-mavenscm||No CI build until needed|
|m2eclipse-subclipse||org.maven.ide.eclipse.subclipse||m2eclipse-subclipse||No CI build until needed|
|m2eclipse-ajdt||org.maven.ide.eclipse.ajdt||m2eclipse-ajdt||No CI build until needed|
(names in bold are odd/inconsistent and may change)
Since there is no usable git team provider (egit is getting better with each release, but is not quite there yet), clone git repository from command line first
Developers with commit access need to use ssh url (eg, email@example.com:sonatype/m2e-core-tests.git). Please check repository homepage at github to find read-only/developer urls for other repositories.
Old, read-only subversion repository is available at http://svn.sonatype.org/m2eclipse
- Get Eclipse 3.7/Indigo "IDE for Java Developers" from http://eclipse.org/downloads/ (comes with m2e 1.0)
- Install tycho, modello and plexus metadata generation integration from m2e marketplace catalog (Preferences->Maven->Discovery)
- Optionally, install EGit from http://www.eclipse.org/egit/download/
Clone one or more git repositories listed above
For m2e-core, import "Existing Projects into Workspaces". For all other repositories, import "Existing Maven Projects"
Use PDE Target Platform preferences (Window->Preferences->Plug-In Development->Target Platforms) page to select target definition.
"m2e-e37" is based on Eclipse 3.7 and is recommended for m2e development
"m2e-e36" is based on Eclipse 3.6.2 and can be used to test compatibility with Eclipse 3.6.x
Once desired target platform is selected, PDE will download all required bundles and features from remote P2 repositories and will use the selected target platform to compile m2e project and run m2e in self-hosted mode. Please note that m2e target platform is over ~200M in size, so download can take very long time.
Self-hosted mode launches another Eclipse application with references to the development workspace projects, in order to debug plug-ins without installing them. The quickest way to do this is to open org.eclipse.m2e.core/plugin.xml with PDE's Plug-in manifest editor and then on the overview page click "Launch an Eclipse application."
To get more control over what you run, use the menu "Run / Run configurations..." and create a new launch configuration using "Eclipse Application" configuration type. You can select the JRE used, set VM properties, and pick the plug-ins to include (use "all workspace and enabled target plug-ins, or select them individually and use "Validate Plug-ins" action to verify if selected configuration is correct).
- In VM Arguments for current target platform: menu Window/Preferences/Plug-in development/Target Platform then select Launching Arguments tab (you can also specify the same arguments in the target platform definition editor, on the Environment tab)
- In the launch profile: menu Run / Run Configurations..., select Arguments tab
Use the following arguments:
To run tests from the IDE, select org.eclipse.m2e.tests test project.
Then right-click, and run "Run As... / JUnit Plug-in test" action from the popup menu. You can use "Debug As... / JUnit Plug-in test" to run tests with debugger. You can also invoke the same actions on individual tests in this project.
One of the tests checks if a J2SE-1.5 execution environment is present, so make sure you have that.
In order to run tests, you need to increase memory for the test JVM as described in the previous section.
|Maven 3.0.1 or newer is required to build m2eclipse distribution!|
To build complete update site using Maven, you need all projects checked out locally. Then switch to org.eclipse.m2e.parent folder and run
That will build all nested modules, including org.eclipse.m2e.site project and if everything succeed, the update site can be found at org.eclipse.m2e.site/target/site/
|Continuous Integration server is building project update site from master HEAD and snapshot builds can be installed from https://repository.sonatype.org/content/repositories/forge-sites/m2e/.|
Page: (Obsolete) Target Platform based on Eclipse 3.4
Page: Contributing Patches
Page: Creating Target Definition in Eclipse
Page: Project Details
Page: Staging and releasing new M2Eclipse release
Page: Target Platform based on Eclipse 3.2
Page: Testing UI with WindowTester