Skip to main content
Jump to: navigation, search

Stardust/Source Code

< Stardust
Revision as of 05:48, 17 September 2013 by (Talk | contribs) (Build Tools)

Browsing the Source Code

For initial quick browsing of the source code please go to

Installing Git

To checkout the source code you need to install git first. You have different options:

  • git scm installs a minimal environment to run Git. It comes with a Bash,a Perl interpreter, the Git executable plus dependencies.
  • msysgit installs a build environment for Git on Windows. It includes git scm.

After installtion you can open a git shell to run git commands (git bash or git-cmd.bat).

Downloading the Source Code

  1. Create a new folder and open a git shell in it. (bash on Linux/Win or git-cmd.bat on Win)
  2. Copy the following commands in a cloneStardust.cmd or file, save it to the folder and run it from there (or run the commands individually)
git clone
git clone components
git clone deploy.jee
git clone documentation
git clone engine
git clone examples
git clone org.eclipse.stardust
git clone ide
git clone ide.simulation
git clone ide.wst
git clone product
git clone
git clone reporting.rt
git clone reporting.ui
git clone repository
git clone ui.common
git clone ui.web
git clone
The above mentioned commands will checkout the master branch per default. Please note that the currently active branche is I_4_3 for Kepler driven builds. You can checkout by adding the "-b <branch-name>" parameter to the git command.

Branch I_4_3 is currently used for the latest Kepler development. For each milestone and release build we are tagging the sources. So if you want to use the stable sources then you have to checkout one of the release tags (at the moment only one exists, namely v1.0.0.20130612-0325-R) you can do this in the Git bash as using:

cd <root-of-your-stardust-checkout>\bin\ checkout v1.0.0.20130612-0325-R

(The script steps into each Stardust repository and executes the git command: git checkout v1.0.0.20130612-0325-R)

When Stardust 1.0.0 was released we merged all changes from I_4_3 into master. From this point on, Master will contain the latest stable release sources and branches like I_4_3 are used as a development branches.

If you run git clone behind a HTTP proxy specify proxy details first.

git config --global http.proxy http://<user>:<password>@proxy:port

Building Stardust

Build Tools

After check out as described above you can build Stardust source code. You need Apache Ant and Apache Maven. If you do not already have those tools installed please download them from their official website and install them accordingly to their installation instructions in a location of your choice, later called ANT_HOME and M2_HOME. We suggest Ant 1.8.4 and Maven 3.0.4, but other similar versions should work as well. After those preparations are done perform the following steps described in readme.txt in the product folder.

Environment-specific Changes

Make sure your environment variables ANT_HOME, M2_HOME and JAVA_HOME are set correctly. Also add ant and maven to your %Path% environment variable. Create a file called in the folder [your stardust git dir]/ Modify the file with a text editor and add the following content:

java16.home=[your java home path]
m2.home=[your maven home path]

for instance:
java16.home=C:/Program Files/Java/jdk1.6.0_32

If you don't want to use the preconfigured Maven settings file [your stardust git dir]/ then you have to specify the path of the actual settings file in your [your stardust git dir]/ file, e.g

mvn.settings=C:/Program Files/Maven/conf/settings.xml

Make sure that you use forward slashes in property files!

Running the Builds

Make sure your machine is connected to the internet, open a command line in your build folder and then execute these two commands replacing [build_tools_home] with the absolute path to your sub folder:

set MAVEN_OPTS=-Xmx768m -XX:MaxPermSize=128m
mvn -f product/components-pom.xml -s [build_tools_home]/conf/m2/settings.xml -P stardust-build[build_tools_home] install

For instance:

mvn -f product/components-pom.xml -s c:/stardustbuild/ -P stardust-build install

Depending on your connection speed and other factors the completion of the second command can take up to several hours.
After build of components finished successfully, you should find the resulting artifacts in your local maven repository at [build_tools_home]/build/m2-repo.

Now the eclipse p2 repository with the Stardust eclipse plug-ins can be built. Run the following command replacing [build_tools_home] with the absolute path to your sub folder:

mvn clean install -f product/pom.xml -s [build_tools_home]/conf/m2/settings.xml -P force-overwrite,stardust-build[build_tools_home]

for instance:

mvn clean install -f product/pom.xml -s C:/stardustbuild/ -Pforce-overwrite,stardust-build

This will trigger the build of the p2 repository.

The above mentioned commands assumes that you're using the Maven settings file which is located in [build_tools_home]/conf/m2/. If you like to use the one of your user home folder or the one of your Maven installation folder (in this case please add the mvn.settings property in [build_tools_home]/etc/ which is described above) then you can remove the "-s [build_tools_home]/conf/m2/settings.xml" parameter from the build commands.

After the build has finished successful, you will find the repository in the sub folder :

[your stardust git dir]/repository/org.eclipse.stardust.modeling.repository/target/repository/

and zipped as an update site:

[your stardust git dir]/repository/org.eclipse.stardust.modeling.repository/target/

Where to go from here?

Now you can use the build result, a local eclipse update site, to install Stardust. Follow the instructions in the section Local Eclipse Update Site (offline)

Next check out the resource in the Stardust Knowledge Base, especially the Getting Started section. You may also want to check out the Forum to post questions or just exchange thoughts with the community.


If you experience any problems downloading the source code or building Stardust then please contact us via the Forum.

Error retrieving BIRT Runtime

If you get the error below or something similar while running the p2 repository build (step 2) then this is caused by an instabilty of the connection with the Eclipse server. Retrying the same build command at a later point in time should resolve the issue.

[ivy:retrieve]  Server access Error: Read timed out 

Errors fetching Dependencies

If you encounter errors during the build that indicate missing dependencies which could not be fetched from the repositories then try cleaning the ivy cache folder .ivy in your user.home (e.g. C:\Users\\.ivy, if it exists) and the maven repository (check settings.xml in M2_HOME/etc and/or user.home/.m2 to determine the location).

If your are using Maven 3.0.4 behind a proxy please see here on how to fix the issue.

Importing projects into Eclipse

After you have executed the build you can import the projects into Eclipse. Although we're using Maven as the main dependency management system we have currently some projects which are using Ivy for the dependency management (this will be slowly but surely changed sooner or later). Because of the fact that the IvyDE plugin can handle Ivy and Maven projects we have adjusted all projects to work with this plugin.

Installing IvyDE plugin

At first you have to install the IvyDE plugin. To do that just click on "Install new Software..." in the Help menu item of Eclipse. In the upcoming dialog press the "Add..." button and provide the following URL Please install "Apache IvyDE" and optionaly "Apache IvyDE Resolve Visualizer". These can be found in the section "Apache IvyDE Eclipse plugins".

Import project

Now import the project with help of the "Existing Projects into Workspace" wizard of the import dialog of Eclipse.

Configure IvyDE plugin

After the installation of IvyDE and the project import, open the preferences dialog of Eclipse which can be found in the Window menu item and click on Ivy in the left panel. Now configure the plugin as follows:

  • Advanced: enable "Use extended resolve id"
  • Classpath Container: enable "Resolve dependencies in workspace"
  • Settings/Ivy settings path: ${}
    • this assumes that you have already imported the project in Eclipse

Importing all projects

In the last step you can import all remaining projects into Eclipse with the "Existing Projects into Workspace" wizard of the import dialog of Eclipse. As the root directory you can choose the GIT checkout folder. As a result of this all projects are listed in the Projects view. Please remove the marker left of the project stardust-hazelcast-ra because it is currently not used. After this click on the "Resolve All" button which can you find in the IvyDE toolbar:


This step can take some time. Therefore we're suggesting to open the Ivy Console in the Console view to see/validate the resolve progress.

Binary Distribution

Stardust v1.0 has been released as part of the Eclipse Kepler release. Further binary distributions will be released together with the following Eclipse releases.

Please see the downloads page for further details.


  • The products libraries have been reviewed for license conflicts.
  • Dependencies that did not comply with the Eclipse Public License (EPL) have been replaced
  • The source has been submitted to the Eclipse foundation where it was reviewed with regards to intellectual property rights and licensing.
  • The source was refactored. All package names were change to the eclipse package names.

Back to the top