Everyone is invited to getting involved with the EMF Client project.
Before you plan any kind of contribution, it is a good idea to contact
the project team
- Writing bug reports: Please provide a short and concise
explanation of the problem, a snippet to reproduce the issue,
ideally a JUnit test case that outlines the expected behavior. See
the support page for details. You are also
invited to enter feature requests.
- Providing a patch to an existing bug report: If you are no
committer on the project, please upload your bug report in the bugzilla
- Contribute documentation, i.e. if you found something which
is not documented yet, please share you knowledge with other users.
Please contact us, to find the
appropriate place to add your documentation.
Developer Resources for the Juno version of EMF Client
Step 1: Download and install Eclipse
Step 2: Additional Plug-Ins
This tutorial describes how to install the workspace for the Juno
branch of EMF Client Platform. Please note that this branch will not
be compatible to version 0.9.x if you want to develop based on version
0.9.x, please see here
Step 3: Check-out the source
Install Checkstyle Plug-In from either the Marketplace
(Help->Eclipse Marketplace...) or from the Checkstyle Updatesite
Step 4: Set the target
You can clone the following GIT repository: If you want to use GIT as
a committer please use the following URI:
If you want to use GIT as an anonymous user (read only) please use the
Select only the "master" branch. Press "Select all"
and proceed with the import.
Please refer to this
to clone GIT repositories.
Now, you can
import the projects from the cloned GIT repository. See here how to
import projects from a GIT repository
Open the _target/ecp.target definition
file. When it is resolved, set this definition as the target platform.
If the target is not resolved, select the emfstore update site and
press update again. The resolution of the target platform takes a
Step 5: Start ECP
For testing, you can use this
. Import it into your EMFCP workspace.
Go to Run->Run
Configurations.. , select the "ECP" launch configuration.
On the plug-ins
tab select the added plugins in the tree view. Then press "Add required Plug-ins".
you are ready to start ECP by pressing "Run".
Extension points - How to
When adding a new extension point please mind the following guidelines:
- The Plug-in ID must be the same as the id of the project defining the extension point.
- The Point ID must not be fully qualified. The name must be camel cased.
- The Point Name must be understandable and give a good hint at what the extension point is doing.
- The Description tab must contain a description for the extension point. If the point is experimental (API not fixed) add the following line:
<b>This extension point is experimental and is likely to change in the future releases as the activity support evolves.</b>
- The Since tab must contain the Version of the plugin since which it is part of the API. (Even if it is experimental). The Version format is maj.min, e.g. 1.1 .
- The Examples tab should contain an example of an usage of this extension point. Use the <pre></pre> tags to display markup.
- The API Information tab should contain a description of classes being used for defining this extension point.
- The Supplied Implementation tab should contain a description of a supplied implementation of this extension point, if one implementation is supplied.
- The Copyright tab must contain the copyright agreement, it look like this:
Copyright (c) 2011-2013 EclipseSource Muenchen GmbH and others.
All rights reserved. This program and the accompanying materials
are made available under the terms of the Eclipse Public License v1.0
which accompanies this distribution, and is available at
The company name must be adjusted if necessary.
You can use HTML tags in all tabs. Use this possibility to improve the readability of your texts.