Skip to main content
Jump to: navigation, search

Platform UI/How to Contribute/Oomph

< Platform UI‎ | How to Contribute
Revision as of 11:54, 23 February 2018 by Bsd.mt.ca (Talk | contribs) (Use Latest)

Setting up your SDK for code contributions

Our goal is to have a completely automated installer for setting up your workspace to contribute to Eclipse. There are still some manual steps in this setup guide but we're working on eliminating them.

Before we start, please note the installer works only on the 64bit version of Java and when the oomph setup files are updated by the platform team. So if you strictly need to use a 32bit version, or if you find the setup is not updated, please, follow the full guide to setup the SDK.

Go to Eclipse Downloads and download the installer for your platform.

Uisetup-1-download eclipse.png

Launch the installer.

If you see a yellow exclamation mark in the top-right, it means the installer is out-of-date. Click on the exclamation mark and then click on the word UPDATE. After the installer finishes updating, it will restart and you can continue with these steps.

Click on the menu button in the upper-right.

Uisetup-2-Installer Screen.png

Click on ADVANCED MODE...

Uisetup-3-Advanced Mode.png

Select "Eclipse Platform"

Select "Latest (Photon)" (not shown in the picture below).

Select the location of a 64-bit 1.8 JDK.

Click Next

Uisetup-4-Select Product.png

Click the checkbox next to the Platform > UI

You may also select other projects in this menu.

Click Next

Uisetup-5-Click The Down Arrow.png

Fill in the "Root install folder" with the parent folder under which you want all your Eclipse installs to go. (If you've run the installer before, it will remember your decision and you won't see this again unless you click "Show all variables").

Fill in "Installation folder name" with the name you want to give this Eclipse installation.

Click on "Platform UI Git or Gerrit Repository" and select the one starting with SSH.

Fill in your gerrit username. Alternatively, if you don't plan to contribute anything back to Eclipse you can use the default selection and omit filling in a username.

Leave the other values set to their defaults.

Click Next

Uisetup-6-Edit Variables.png

Click Next, Click Finish.

Accept the license agreements.

Wait for the message "Press Finish to close the dialog" then do that thing.

Wait for the new Eclipse workspace to start up, initialize, and build.

Launching Eclipse

When you want to launch Eclipse again, you'll find the executable in the "Root install folder" you selected above. The executable will be here:

<Root install folder>/<Installation folder name>/eclipse

For example, if I'm on Linux and selected ~/oomph for my root install folder and platform-master for my installation folder name, the executable I launch to run Eclipse will be called:

~/oomph/platform-master/eclipse/eclipse

Running specific builds

Following the steps above will put you on the integration build stream and cause your copy of Eclipse to auto-upgrade to each new integration build. If you want to always be using a specific integration build or - say - a the nightly build stream, follow these steps after you've finished installing Eclipse as described above.

Go to the download site for the integration build you wish to use (or any nightly build if you want to be on the nightly build stream).

The download page for each build will contain two links to update sites. One is for the stream (which always points to the latest build of that type) and the other is for that specific build. Copy the URL for the one you want. The links look like this on the download page:

Upsetup-Eclipse Download Page.png

Go to Window > Preferences > Install/Update > Available Software Sites Add... Paste the URL of the update site and type in any name. Click OK > OK Go to Help > Check for updates Install any updates it finds Restart Eclipse if prompted

You will then be running the specific build you selected. If you selected a stream rather than a specific build, you can update to the latest build of that type by rerunning the "Check for updates" command. If you selected an older integration build, you may want to de-select the 4.7 I-builds update site to prevent Eclipse from auto-updating to a newer integration build.

Active branches

Our currently active branches:

  • master - development towards the next release
  • R4_6_maintenance - fixes for 4.6.x/Neon service releases, no active development but sometimes we cherry pick patches from master to it

Back to the top