Skip to main content
Jump to: navigation, search

Difference between revisions of "Building the STEM RCP Application"

(New since STEM 4.0.0)
(New since STEM 4.0.0)
Line 48: Line 48:
# add your public key
# add your public key
'''for committers''' by HTTPS
Or '''for committers''' by HTTPS

Revision as of 18:44, 7 January 2019


Weekly Build

Weekly STEM builds are regularly posted on the STEM website (about weekly).

Please see the category Weekly Integration Builds on the STEM download site


If you are a developer and have already installed and run from the development environment, 
you can create your own build for supported platforms.  After first following the instructions 
for Running STEM from the Development Environment: 
# please go to the project  org.eclipse.stem.ui
# Open the file stem.product
# On the right hand side click the link: "Eclipse Product export wizard"
# select a destination directory
# click finish

New since STEM 4.0.0

With the introduction of STEM 4.0, Stem is structured as a maven project containing two subprojects:

  - org.eclipse.stem

Both of them are maven projects. Project source code can be imported:

import >>>> Git >>>>> project 
from Git using

Or for committers by SSH


be sure to upload your public key to:

  1. click your name
  2. go to settings
  3. click on SSH keys
  4. add your public key

Or for committers by HTTPS


Stem as a Maven project is using Tycho to make its build "pomless" (meaning it is not required to have a pom.xml file for each Java project).

To build the STEM product

  • right click on org.eclipse.stem.general
  • and run as >>>> maven build >>>

this will open another window to define which command can be used to run the build normally it is enough to write ?clean verify? in the Goals field then click run

STEM data is still built using Ant as described previously see STEM_Eclipse_Setup#Build_the_STEM_Denominator_Data

Back to the top