Follow these instructions to set up an Eclipse ESCET development environment.
To create a development environment for the first time:
Get the Eclipse Installer:
Go to https://www.eclipse.org/ in a browser.
Click on the big Download button at the top right.
Download Eclipse Installer, 64 bit edition, using the Download x86_64 button.
Start the Eclipse Installer that you downloaded.
Use the hamburger menu at the top right to switch to advanced mode.
When asked to keep the installer in a permanent location, choose to do so. Select a directory of your choosing.
The Eclipse installer will start automatically in advanced mode, from the new permanent location.
The Eclipse installer will restart in advanced mode.
Continue with non-first time instructions for setting up a development environment.
To create a development environment for a non-first time:
Ensure you are using the latest version of the Eclipse Installer:
One option is to download it again, as per the 'first time' instructions above.
Another option is to update your existing Eclipse Installer. In the Eclipse Installer, when in advanced mode, click the 'Install available updates' button. This button with the two-arrows icon is located at the bottom-left part of the window, next to the version number. Wait for the update to complete and the Eclipse Installer to restart. If the button is disabled (grey), you are already using the latest version.
In the first wizard window:
Select Eclipse Platform from the big list at the top.
Select 2023-03 for Product Version.
For Java 17+ VM select JRE 17.x.x - https://download.eclipse.org/justj/jres/17/updates/release/latest.
Choose whether you want a P2 bundle pool (recommended).
In the second wizard window:
Use the green '+' icon at the top right to add the Oomph setup.
For Catalog, choose Eclipse Projects.
For Resource URIs, enter
https://gitlab.eclipse.org/eclipse/escet/escet/-/raw/develop/org.eclipse.escet.setupand make sure there are no spaces before or after the URL.
Check the checkbox for Eclipse ESCET, from the big list. It is under Eclipse Projects / <User>.
At the bottom right, select the develop stream.
In the third wizard window:
Enable the Show all variables option to show all options.
Choose a Root install folder and Installation folder name. The new development environment will be put at
Fill in the Eclipse ESCET Git clone URL:
Committers with write access to the Eclipse ESCET official GitLab repository can use the default URL
Contributors can use the same URL, but as they don’t have write access, they will not be able to push to the remote repository. They can instead make a fork of the official Git repository, as described in the contributing section. Then they can fill in the URL of their clone instead, i.e.
<username>replaced by their Eclipse Foundation account username, and
<cloned_repo_name>replaced by the name of the cloned repistory, which defaults to
For Eclipse Foundation account full name fill in your full name (first and last name) matching the full name in your Eclipse Foundation account. This will be used as name for Git commits.
For Eclipse Foundation account email address fill in the email address associated with your Eclipse Foundation account. This will be used as email for Git commits.
In the fourth wizard window:
Wait for the setup to complete and the development environment to be launched.
If asked, accept any licenses and certificates.
If you get a Trust dialog, click Select All and then Trust Selected.
Press Finish in the Eclipse Installer to close the Eclipse Installer.
In the new development environment, observe Oomph executing the startup tasks (such as Git clone, importing projects, etc). If this is not automatically shown, click the rotating arrows icon in the status bar (bottom right) of the new development environment.
Wait for the startup tasks to finish successfully.
NOTE: If you don’t open the Oomph dialog, the status bar icon may disappear when the tasks are successfully completed.
If you have any issues during setting up the development environment, consider the following:
You can set the following environment variables to force the use of IPv4, in case of any issues accessing/downloading remote files:
After setting them, make sure to fully close the Eclipse Installer and then start it again, for the changes to be picked up.
In your new development environment, consider changing the following settings:
For the Package Explorer view:
Enable the Link with Editor setting, using the icon.
Enable showing resources (files/folders) with names starting with a period. Open the View Menu () and choose Filters…. Uncheck the
.* resourcesoption and click OK.