Copyright © 2009, 2010, 2011, 2012, 2013, 2014 vogella GmbH
Table of Contents
As the Eclipse project is an open source project, it is possible to get the source code, modify it and provide the change back to the project. Eclipse projects typically use a review process based on the Gerrit code review system to review the changes and, if the change fits into the project goal, apply it once it has been polished.
Contributing to an Eclipse project has the benefit of getting feedback directly from the core developers. It also allows developers and organizations to fix bugs which affect them and to drive the project into a desired direction.
The development of the individual Eclipse projects is done by the Eclipse developers - companies and individuals alike - which develop the code.
The Eclipse project distinguishes between the following group of people:
Eclipse User - Using at least one product, e.g., a
file, of the Eclipse project. Eclipse users consume the software
created by the Eclipse
developers but do not help with the Eclipse
Contributor - Submits code corrections, write documentation or file bug reports. A contributor does not have access right to submit code directly to an Eclipse project.
Committer - Has been trusted with reviewing patches and the privilege to make changes without going through code review.
Everyone has read access to the code repositories hosted at eclipse.org.
Eclipse projects use the Git version control system. Eclipse lists all Eclipse Git repositories under the following URL: Eclipse source code repository.
To find the URL for cloning the Git repository of a project, you can search in this webpage. For example, if you want to clone the e4 tools Git repository, you can search for e4 and click on the e4.tools repository.
If you click on the project, you see the details of this project, e.g., the commits. At the bottom of the page you also see the URL to clone the repository.
The URL listed in this part is not optimized for Gerrit contributions. See Section 11, “Clone a selected Eclipse Git repository” for a better way to clone in case you want to contribute via Gerrit.
The Eclipse IDE is an open source (OS) project. Eclipse.org hosts lots of OS projects with different purposes, but the foundation of the whole Eclipse IDE is delivered by the Eclipse platform, the Java development tools (JDT) and the Plug-in Development Environment (PDE) project.
All these projects belong to the project called "Eclipse project". The name is a bit strange since nowadays there are many Eclipse projects. But it originates from the fact that these projects are at the beginning the only available Eclipse projects.
These components are bundled together as the Eclipse Standard Development Kit (SDK) release. This is also known as the Eclipse standard distribution. The Eclipse SDK contains all tools to develop Eclipse plug-ins.
In addition to these projects, the platform also has an incubator project called e4 which provides new tools for Eclipse 4 developments. It also serves as a testing ground for new ideas.
Despite the general assumption that the Eclipse SDK components are developed by an army of developers, the actual core developer team is relatively small.
General information about an Eclipse project can be found under http://projects.eclipse.org/. For example via the Members link you can see the project lead and the most active committers. For example, the information for the platform project can be found under the Eclipse project link.
Since the core team is relatively small, contributors can really make a difference.
To find out how many people contribute to a given Eclipse Git repo you can use the following command on a Linux like system. For example running this command shows 27 on July, 07, 2014 result in 27 people contributing to the platform.ui repository.
git log --since='last 3 month' --raw | grep "^Author: " | sort | uniq -c | wc -l
It is possible to see the contributions by individual Git
for example, as depicted in the following screenshot for
project, which can be reached via
Eclipse platform.ui project page.
An alternative view gives the new dashboard. For example the following screeenshot shows the Platform.ui dashboard link.
The Eclipse project has a simultaneous release every year at the end of June. In June 2014 the Eclipse 4.4 (Luna) version was released.
The Eclipse project creates regular builds of the next releases. You find Stable Builds which are tested by the community. These milestone (ending with M and a number) and release candidate (RC) builds are created based on a predefined time schedule.
Integration (I) and Nightly (N) builds are test builds which are automatically created. They are not manually tested.
In general, milestone and RC builds are relative stable compared to integration builds, but may not contain the latest features and patches.
To contribute to the Eclipse open source project, you need to download one of the recent integration or milestone builds. The official Eclipse release typical don't compile the latest code, because too many dependencies have changed.
You find one of latest M or RC builds under the Eclipse project download page link.
Directly after a new Eclipse release, you will not find M or RC builds. The first milestone build is typically created 6 weeks after the official release.
Typically M or RC builds should be good enough, except when you want to try out bleeding edge things.
You can download the latest integration build for the next Eclipse release under the following URL: Eclipse developer builds .
This is sometimes necessary to test the latest features or to test a build which is later promoted to M or RC build by the Eclipse platform team.
The Eclipse SDK development requires that certain plug-ins are installed in your IDE. These plug-ins include for example the Mockito test library. The latest Eclipse SDK does also not include the Git tooling which needs to get installed separately.
You should also install the e4 tools as they provide tools for developing Eclipse 4 components.
You find a recent version of the e4 tools under the following
http://download.vogella.com/luna/e4tools. For newer versions check the
The above URL has been created by the vogella GmbH company to provide a
stable update site. You find the
official update sites for the
Eclipse e4 tooling
project under the following URL:
The Eclipse platform team provides a file from which these plug-ins can be installed. Download the following file: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/plain/releng/org.eclipse.ui.releng/platformUiTools.p2f
You can install the plug-ins described by this file by using→ → → .
Like in every successful open source project you have different possibilities to contribute to the Eclipse open source project. This chapter gives an overview of the possible options.
Non of these options are exclusive. Active Eclipse committers and contributors typically do all of them, e.g., answers questions in the forum, open bugs, update the wiki pages, etc.
The Eclipse forums offer several topic-specific forums in which you can post and answer questions. To post or to answer questions in the Eclipse forums, you need a valid user account in the Eclipse bug tracker.
Stack Overflow also requires a user account and its community is also very active. Stack Overflow does not have separate forum sections for specific questions. At Stack Overflow you tag your questions with the relevant keyword, e.g., Eclipse and people search for them or subscribe to them.
Another way of contributing to the Eclipse open source project is to update the Eclipse Wiki and to write about Eclipse tips and tricks you find useful.
Another way to contribute to Eclipse is to write articles or blog posts about it. PlanetEclipse is a blog aggregator which collects new posts about Eclipse. If you blog about Eclipse you can ask to get aggregated at PlanetEclipse. Just click on the highlighted link to get started.
If you find problems or have an idea on improvements in an Eclipse project you can open a new bug report at the Eclipse bugtracker.
As example you can report bugs for the Eclipse platform via the following link: Bug report for the Eclipse platform .
If you are interested to help with bug solving, most Eclipse projects have a huge backlog of existing bug reports. It is often not possible for the committer to re-test all old bug reports. A contributor can re-test bug reports and report if they are already solved.
People which are interested in this activity should contact the email distribution list after re-testing a few bugs. Committer can nominate them to get the right to close bug reports form from others. See Eclipse bug triage for the nomination process.
This is also a valuable preparation step to contribute code fixes to the Eclipse project.
Once you have cloned a Git repository from Eclipse, you can import the related projects and start working on them.
After you finished a code contribution, you can commit the change locally and push it to Gerrit so that the Eclipse developers can review your change.
This book focus on the contribution of code to the Eclipse project. The Eclipse platform project is used for the exercises and examples but the process should be applicable for almost all Eclipse projects.
In this exercise you use the Bugzilla system to review some of the Eclipse platform bugs. No action is excepted from you, but if you find an updated bug, you should update the bug report and describe that the problem is solved.
This exercise uses the Eclipse platform as example but you can use any Eclipse project of your choice.
Open to Eclipse Bugzilla and select the Search button. Select the Advanced Search tab and search for → → for all bugs in status NEW, ASSIGNED and REOPENED.
Review at least 10 bugs from the result list. Try to reproduce the issue, if the bug reports a software error. If you are unable to reproduce the bug, add a comment in the bug that you cannot reproduce it.
After you commented on the outdated bugs, wait for a few days (or weeks) for the reaction of the existing Eclipse committer.
If your analysis of the bug was correct and you found several outdated bugs, you have proven that your analysis tends to be correct. In this case you could also request the right to close bugs directly. This is typically done via the https://dev.eclipse.org/mailman/listinfo/ Eclipse project mailing list, e.g., Platform UI mailing list for this example. Send a short email to the list, describing that you would like to help with the bug reports and lists the bugs you contributed to.
Most Eclipse.org projects and all Eclipse platform projects use the Gerrit code review system for contributions. Gerrit makes the process of contributing relatively simple (after the initial setup). It makes also reviewing these contributions very easy for the Eclipse committers.
In theory you can also provide patches via Bugzilla, but experience has shown that patches are not that actively reviewed compared to Gerrit changes. Gerrit changes are easier to review and to update for both sides, hence committers are more likely to review Gerrit changes. Some projects, like Nebula, and JGit, EGit have stopped accepting patches through Bugzilla completely.
To contribute, you need to configure your Bugzilla and Gerrit user, this process is described in this chapter.
You need to create an Eclipse.org user account to contribute to an Eclipse project via the following URL: Create Eclipse.org user account .
If you already have an Eclipse Bugzilla or Eclipse Forum account, you have already done this step. These systems use the same account.
You also need to sign a contributor license agreement (CLA) via a web interface.
With the CLA you confirm that you have the rights to contribute source code to the Eclipse open source project.
In case you contribute to the Eclipse open source project during your work time, ensure that your employer agrees that the code can be contributed.
The Eclipse CLA FAQ describes the process and purpose of the CLA. At the end this document contains a link for signing the CLA. You find it under the following URL: Eclipse CLA FAQ.
After signing the CLA you are allowed to contribute code to the Eclipse platform project via Gerrit.
The CLA signatures are cached on the Eclipse servers. It can take up to 10 minutes for your CLA signature to be refreshed, i.e., if you sign the CLA and try to push immediately you may receive an error message, that you did not sign the CLA.
The user name registration and CLA signing is not required for cloning the Eclipse repositories and for modifying the code in your local Git repository. They are only required for contributing a Gerrit change.
You have two options to authenticate with the Eclipse Gerrit server. You can either use SSH or HTTPS.
To configure these access methods open the following URL: Gerrit at Eclipse.
Login with your Eclipse account (registered email address) and password.
Afterwards select Settings as highlighted in the following screenshot.
Select Profile and note down your user. This user is later required for the push configuration.
The Gerrit user is NOT the same as your Eclipse user. Also, the Gerrit HTTPS password is NOT the same as your Eclipse user password.
You can either use SSH or HTTPS to push to Gerrit. See Section 10.2, “Authentication via HTTPS” for the configuration of HTTPS and Section 10.3, “Authentication via SSH” for the configuration of the SSH access.
If you are not familiar with SSH, the HTTPS authentication is typical easier to configure to get started. If you use HTTPS you will have to enter you password for operations with Gerrit, this can be avoided with SSH. If your company is using a proxy it may be difficult or impossible to use ssh.
The Gerrit review system enables you to generate an HTTP password. Select the HTTP password in the Gerrit user settings and generate a password. This setting is depicted in the following screenshot (the password is obfuscated).
Note down this password; as you need it to push your changes to the Eclipse Gerrit system. You can visit this page later if you forgot the password.
If you are not planning to use HTTPs authentication it is recommended to clear the password or never to generate it so that this login method is effectively disabled.
This is an alternative to Section 10.2, “Authentication via HTTPS”. If you want to use HTTPS with a password, please skip this and the next section.
You need to upload your SSH key to the Gerrit installation so that you can push changes to Gerrit via SSH. If you are not familiar with SSH please see Section 10.4, “Authentication via SSH”.
Once you have created a SSH key pair, upload your public SSH key to Gerrit to be able to push to it.
Most Git (and Gerrit) servers support SSH based authentication. This requires a SSH key pair for automatic authentication.
An SSH key par consists of a public and private key. The public key is uploaded to the application you want to authenticate with. The application has no access to the private key. If you interact with the hosting provider via the ssh protocol, the public key is used to identify a user who encrypted the data during communication with the corresponding private key.
To create an SSH key under Linux (or Windows / Mac with OpenSSH
installed) switch to the command line and
The generated SSH
key is by default
located in the
directory of the user home directory. Ensure that you backup existing
before running the following commands.
# Switch to your .ssh directory cd ~/.ssh # If the directory # does not exist, create it via: # mkdir .ssh # Manually backup all existing content of this dir!!! # Afterwards generate the ssh key ssh-keygen -t rsa -C "firstname.lastname@example.org" # Press enter to select the default directory # You will be prompted for an optional passphrase # A passphrase protects your private key # but you have to enter it manually during ssh operations
The Eclipse IDE allows you to create an SSH key pair via→ → → → .
It is good practice to use a
passphrase to protect your
private key. It
is also good practice to
operating system level permission settings
to ensure that only
owning user can access the
folder and its content.
In the above
command the -C parameter is a comment. Using your email is good
practice so that
someone looking at your public key can contact you
case they have
questions. Including the email enables system
to contact the person in case of questions.
The result will be two files,
which is your private key and
which is your public key.
You can specify alternative key names with the
parameter on the
This is helpful if you have multiple
repositories and you
want to have a different key for each
example, you can name
your SSH keys in domain
as well as
additional configuration in the
will be picked up by
default. The following code shows an
Host *.eclipse.org IdentityFile ~/.ssh/eclipse.org Host *.github.com IdentityFile ~/.ssh/github.com
To find the correct URL to clone a repository from Gerrit, go to the Gerrit Eclipse homepage and select the → menu entry. Afterwards search for the project. In the depicted screenshot, the search is done for the Eclipse platform.ui repository.
Once you found a project you can click on it and select SSH or the HTTP tab to see how you can clone that. The selection for SSH is depicted in the following screenshot.
The selection for HTTPS is depicted in the following screenshot.
Note that the URL automatically includes your user name. This makes it easier to push later a commit to the Eclipse Gerrit review system.
In case you cloned a Git repository without using the Gerrit URL as described in this section you have to adjust the push URL. See Section 20, “Cloning from the Git server and adjusting the push URL” for a description how to do that.
You can also clone anonymously, if you just want to play with the source code locally and do not intend to contribute changes.
The Gerrit server requires that you push using a predefined refspec, called HEAD:refs/for/master. A refspec allows you to configure which remote branch should be used for remote operations.
The Eclipse tooling allows you to set this up more or less automatically.
Select your remote repository in the Git Repositories view, right-click on it and select Gerrit configuration.
If you select the origin entry, right mouse click on it and select Gerrit Configuration... the entry should look like the following screenshot.
For HTTPS access the URL is different.
You can validate the Push Specification if you select the highlighted node in the following screenshot and check the Remote Push Specification entry in the Properties view.
Also the icon for the repository changes to a green one and Gerrit specific commands are added to the repository's context menu, e.g., Push to Gerrit... and Fetch from Gerrit...). In addition, the repository is configured to always add a Change-ID to the commit message.
screenshot the repositories configured for
repository in this screenshot is not configured for Gerrit.
Make a code change (fix) which you want to upload to Gerrit.
Find a very simple change for your first contribution. For example fix a typo or a compiler warning.
Assuming you did a code change and performed the Gerrit configuration, you can now push to the Gerrit review system.
The easiest way is to use the Git Staging view. In this view you see all the changes you did and you can drag and drop files to the Staged Changes part.
You need to sign off every commit. The Git functionality in Eclipse simplifies that via the sign-off push button. The Add Change-Id push button allows you to include a Change-Id entry to the commit message. Both buttons are highlighted in the following screenshot.
The Change-ID entry is initially set to "Change-Id: I0000000000000000000000000000000000000000". During the commit, this is replaced with an ID generated by the Git tooling. Like other Git IDs it is a SHA1 over the content it captures and the letter 'I' is added a prefix to make it obvious that it is a Gerrit Change-Id and not a Git commit ID.
To get picked up by Gerrit, the Change-Id must be in the last paragraph together with the other footers. To avoid problems do not separate it from the Signed-off-by message with a new-line character.
If you want to react to review comments and improve the initial commit you pushed for review use commit amend to create an improved commit and push it again to Gerrit.
Since the amended commit contains the same Change-Id as the initial commit, Gerrit knows that you want to update this change with the new commit. Also in your local Git repository commit amend replaces the previous commit in your local history (and keep the same parent commit).
The most important Eclipse platform repositories are listed below.
# the links below are web links intended to be opened by a browser # the pages contain URL for cloning the repositories # at the bottom of the page # NOTE better get the Git URL via http://git.eclipse.org/r because # that URL contains also your user. That allows you to contribute back easier # Eclipse platform UI repository # contains JFace, Eclipse user interface, example projects # and related tests http://git.eclipse.org/c/platform/eclipse.platform.ui.git/ # Eclipse platform runtime # contains the Equinox runtime, the dependency injection engine, # the non user interface related services and related tests http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/
The most important JDT repositories are listed below.
# the links below are web links intended to be opened by a browser # the pages contain URL for cloning the repositories # at the bottom of the page # NOTE better get the Git URL via http://git.eclipse.org/r because # that URL contains also your user. That allows you to contribute back easier # JDT user interface http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/ # JDT core # hosts the Eclipse java compiler http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/ # JDT debug http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/
Most Eclipse projects provide a test suite which can be used to validate that everything still works as planned.
For example, in case you are changing the Eclipse platform code you should ensure that the platform tests still perform as planned. If changes in the tests are required, you should adjust the tests with the same Gerrit change.
At the time of this writing, lots of unit tests of the Eclipse projects are still based on JUnit 3.x. JUnit 3.x uses the test prefix of method names to identify test methods.
It is planned to migrate the Eclipse platform tests to JUnit 4 in the future, see the Convert Eclipse platform.ui test suite to JUnit 4 bug report for the discussion.
On Unix based system you can also run the user interface tests with a virtual display. This makes the execution of the tests faster and allows to developer to continue to work on the same machine.
This step is optional. You can of course run the tests without a virtual server.
The Eclipse platform unit tests starts an Eclipse IDE and visually interacts with it. This screen flickering can be annoying. You can use a virtual server and execute the tests on this virtual device.
On Ubuntu you can install the virtual server and the client via the following commands. The client is not required to run the unit tests but useful in case you want to view the test execution on the virtual server.
# install the server sudo apt-get install vnc4server # optionally install the client sudo apt-get install xtightvncviewer
You start the server with the following parameters.
# start the server on display #1 vncserver :1 -name testing -depth 24 -geometry 1280x1024
In the Eclipse launch configuration you can define the display which is used for the test execution.
If you are running a Maven / Tycho build from the command line, you can export the display variable.
If you want to watch the unit tests, you can also connect to the virtual server via the vncclient.
# connect to the server, IP will be asked vncviewer
Clone the following Git repositories as these contain the existing unit tests. The clone URLs (these are not URLs for the browser!) are listed below.
In case you want to contribute Gerrit patches to these projects, you should clone them via the Gerrit system as described in Section 11, “Clone a selected Eclipse Git repository”. But you can always adjust the push URL later, as described in Section 20, “Cloning from the Git server and adjusting the push URL”.
In this section the procedure to run the unit tests of the JFace components is described as an example for running tests from an Eclipse project.
The unit tests for the JFace Bundle are placed in the org.eclipse.ui.tests plug-in. This plug-in includes also several other tests for the Eclipse platform.ui component.
To run theses tests, import the following required plug-ins:
To test the full JFace TestSuite, you only need to run the
run configuration from the
The performance tests allow you to analyze the performance of various actions, e.g. UIStartup, of the eclipse platform.
To run the tests you have to choose the perfAllTests.java file from the org.eclipse.core.tests.runtime bundle
As a result you get detail performance information like the following from the console:
Scenario 'org.eclipse.core.tests.runtime.perf.UIStartupTest.testUIApplicationStartup' (average over 1 samples): System Time: 16.037,55d (no confidence) Used Java Heap: 91,25M (no confidence) Working Set: 446M (no confidence) Elapsed Process: 11,93s (no confidence) Kernel time: 750ms (no confidence) CPU Time: 27,7s (no confidence) Hard Page Faults: 22 (no confidence) Soft Page Faults: 172,24K (no confidence) Text Size: 4K (no confidence) Data Size: 0 (no confidence) Library Size: 3,79G (no confidence)
Eclipse provides a Maven based build system for automated build using the Maven Tycho plug-in. This effort is called the Common Build Infrastructure (CBI) and intents to provide tools to simplify and standardize the Eclipse build system.
This build system allows you to create your custom version of the Eclipse IDE. The results of this build are archive files for the different platforms, which include everything to run an Eclipse IDE. The resulting IDE is based on the source code of the current development status.
As the build continuously changes, the results and requirement of the build might be slightly changed at the time you read this. See Section 18.1, “Reporting issues or asking questions about the build” for finding additional information.
The build itself takes around 2 hours on a Core i5 machine with SSD, so of course time is required for this. Also, approximately 25 Gigs of free space and 4 Gigs of RAM are required on the hardware-side. Building of an Eclipse IDE is possible on Windows, OS X and Linux based distributions. This tutorial is tested with Linux.
On the software-side the following software is required:
Check if your JVM runs in Server mode, by checking the version.
java -version java version "1.7.0_09" Java(TM) SE Runtime Environment (build 1.7.0_09-b05) Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
You also have to assure that Maven has enough memory, to avoid a
You download the newest version of the source code by cloning the folllowing repository and it's submodules via Git.
git clone -b master --recursive git://git.eclipse.org/gitroot/platform/eclipse.platform.releng.aggregator.git
If the build is successful, the Eclipse SDK is packaged as archive files for all supported platforms. These packages can be found in the Git repository in the following folder:
To ensure that the repository is clean and up to date we execute the following Git commands.
git submodule foreach git clean -f -d -x git submodule foreach git reset --hard HEAD git clean -f -d -x git reset --hard HEAD
The build requires that the version numbers of each single Maven artifacts and it's Eclipse plug-ins are in sync. But sometimes (this is rare these days) developers forget to update the Maven version numbers. In this case the build complains about a version mismatch. Run the following command to correct existing inconsistencies.
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:update-pom
A good place to post questions about the CBI build is the CBI mailing list. The webinterface for this mailing list can be found under the following URL CBI mailing list.
The Eclipse platform has a Hudson build instance which can be found under the following URL: Eclipse platform Hudson. This build instance is currently not used for the main build, only to validate Gerrit contributions.
To have a reproducible and stable build, it is possible to switch to a specific version instead of using the newest source code. For this the platform aggregator repository has tags for every release build.
To build for example the R4_3 release, you have to checkout this specific tag out and start the build like the following:
git checkout tags/R4_3 git submodule update #run the build mvn clean verify
The CBI build still depends on external resources like p2 update sites. From time to time this resources change or will become unavailable. The R4_3_1 tag for example depends on a removed update site, so you have to add the new URL via a parameter to the build:
git checkout tags/R4_3_1 git submodule update # run the build # command must be issued in one line mvn clean verify -Dlicense-repo.url=http://download.eclipse.org/cbi/updates/license/
To check which properties can be overridden check the properties fields in the eclipse-platform-parent/pom.xml file.
A normal CBI Build shows, "Build id: @build@" in the "About Eclipse
SDK" window. To define a custom build id use the
parameter and the
mvn clean verify -DbuildId=foobar -Pupdate-branding-plugins
It is also possible to build just single parts of the aggregator
repository, by passing the
The following example shows how to build just the
cd rt.equinox.framework \ mvn -Pbuild-individual-bundles clean verify
Unfortunately while there are numerous bundles for which the build succeed with this method, there are a couple bundles / features that cannot be built using this method.
The CBI build does not build natives by default (SWT binary files). Instead, the CBI build simply copies pre-built native files from the swt.binaries repository.
For Windows/Mac/Linux it is possible to force the CBI build to
natives by passing the -Dnative pointing to the build.
case of Linux. List of options available at
The Fedora project has removed some non Eclipse IDE related plug-ins to speed up the build process. See the Fedora build script.
The e4 tools project provides tools for developing Eclipse 4 based applications. The following follows more or less the same guidelines as the Eclipse platform team.
The e4 tools are also available as via their Git repository.
# Eclipse e4 tooling git clone git://git.eclipse.org/gitroot/e4/org.eclipse.e4.tools.git # Some e4 demos, not required, not always working git clone git://git.eclipse.org/gitroot/e4/org.eclipse.e4.ui.git
Most e4 tools project contain a
file which describes their usage and important classes.
plug-in defines the
extension point, which allows registering editors for new model
You can build the e4 tools locally via Maven Tycho. If you have Maven installed on your machine, the build process is trivial.
Clone the e4 tools project with the following command.
# clone e4 tooling git clone git://git.eclipse.org/gitroot/e4/org.eclipse.e4.tools.git
Afterwards, you can build the e4 tools via Maven on the command line.
cd org.eclipse.e4.tools mvn clean verify
After the build finishes successfully, you find a p2 update site in the following folder.
Eclipse also has a Hudson job configured which runs the daily builds. See https://hudson.eclipse.org/platform/job/deploy-eclipse-e4-parent/
If you cloned an Eclipse Git repository directly from the Eclipse Git server (without using the Gerrit server) you have to adjust the push URL to create Gerrit changes. For example, you may have found the clone URL on: Eclipse Git web interface.
It is far easier to clone from the Gerrit server as this does not require you to change the push URL. See Section 11, “Clone a selected Eclipse Git repository” for the description how to clone. In case you can use the Gerrit server, this section is not relevant for you.
The push configuration in the following dialog depends a bit if you want to use SSH or HTTPS. If you want to use SSH ensure to use the 29418 port and remove the "gitroot" string from the push-url.
The following screenshot demonstrates that for the Eclipse platform UI Git repository.
If you want to use HTTPS to push to the Gerrit server, you have to use a push URL with an "r" included (For example https://email@example.com/r/platform/eclipse.platform.ui.git). You need to provide in this case your Gerrit password if you want to push to an Eclipse Git repository as depicted in the following screenshot.
Writing and updating these tutorials is a lot of work. If this free community service was helpful, you can support the cause by giving a tip as well as reporting typos and factual errors.
If you find errors in this tutorial, please notify me (see the top of the page). Please note that due to the high volume of feedback I receive, I cannot answer questions to your implementation. Ensure you have read the vogella FAQ as I don't respond to questions already answered there.