Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

Setup for development of Ergo 4.0

  1. Download Eclipse. You should download the latest version of Eclipse, which as of this writing is Eclipse Luna Mars that you can download here. Select the Eclipse for RCP and RAP developers download for your system specification.
  2. Install Eclipse. Unpack the Eclipse zip file, find the folder where you unzipped it, and launch the IDE.
  3. Select a workspace. The default is fine; however, you may want to consider naming it according to your development project (e.g. ergo-workspace) to distinguish it from other workspaces.
  4. There are two Eclipse features that you will need to install before proceeding to the next section. 
    1. Go to Help -> Install New Software...
    2. Where it says Work with: select Luna Mars
    3. Expand Modeling and select Graphical Editing Framework GEF SDK and Graphical Editing Framework Zest Visualization Toolkit SDK.
    4. Click Next, Click Next again, accept the license and Click Finish. After installing the plugins, restart Eclipse when it asks you to do so.

Checking out Ergo projects with Git

The plugin projects for Ergo can be checked out from the following Git repository:


  1. File > Import > Git > Projects from Git and click Next.
  2. Select Clone URI and click Next.
  3. If you haven't yet cloned the repository to your machine, do the following:
    1. Go to, login to your account on opensource and select the repository you want to clone (e.g. ergo).
    2. In the menu on the left side of the page, under Actions, select CLONE and copy the link. It should look something like ssh:// for the ergo repository. If you only want read-only access, you can follow these steps, but don't login to opensource.
    3. Go back Eclipse and paste the link Under Location: URI:  for read-only access -  for  for developer access- ssh://
    4. Under Authentication: User:  If you will be contributing source code, you should create a user account at and specify your username for opensource. If you used the read-only link, you can ignore this part.
    5. Under Authentication: Password: leave it blank if you are using the read only link, or your password if you are a developer and used the ssh link.
    6. Click Next.
  4. Choose the branches you want to clone. For the initial setup, check the box next to master and develop-v1 and click Next.
  5. Where it says Destination, change the Directory from "/home/user/git/(repository-name)" to "/home/user/ergo-workspace/git/(repository-name)". This assumes you used ergo-workspace as your new workspace, if not, replace ergo-workspace with the name of the workspace you created. The Directory inside the dialog box should look similar to /home/user/ergo-workspace/git/ergo if you are cloning the ergo repository. This will keep your git clones inside the workspace (recommended, but not required). After modifying the Directory field, Click Next. Note: If you use the Browse button to select the location, you will need to browse for your workspace and create a folder inside your workspace folder called git and select the git folder. Either way, your Directory field should show /home/user/ergo-workspace/git/ergo
  6. Select Import existing projects and click Next
  7. Uncheck the box Search for nested projects and Click Finish.

Note:  While trying to clone the repositories, if you see the error 1: incorrect URL 2: no network connection 3: SSH is not configured correctly, you need to modify your SSH2 preferences in Eclipse to point at your .ssh folder and your private key(s). For help with this, see ssh2-preferences.

Creating a Fork of Ergo

If you are a developer interested in Ergo, but might not want your changes included in the master repository right away, then you may want to fork the Ergo repository. The only changes to the above would be you would go to and create a Fork of each repository before cloning. When creating your fork, it is recommended that you check the box to "Enable fork syncing". This will keep branches and tags in sync with the branch you forked (presumably master). This path is not recommended if you intend to make continuous contributions to Ergo because forks are usually intended to take development a very different direction than the main development branch. Thus, developers are encouraged to sign the license agreement found here so you can contribute to the master branch by creating feature branches from it and help guide the development process through interactions on the ergo-dev mailing list.

Code Format

Setup Ergo code formatter and cleanup profiles as specified in the Developer Guidelines