Version 15 (modified by welberge, 7 years ago) (diff)



AsapRealizer makes use of the following git and svn repositories:

  • Asap: git repository for the Asap sources
  • AsapDemo: git repository for demonstration programs for the AsapRealizer or other parts of Asap
  • asapresource: git repository for asap specific data
  • asapshared: git repository on which asap binaries (e.g. jar files) are released
  • Hmi: git repository of the Hmi source (used by Elckerlyc and Asap)
  • HmiDemo: git repository for demonstration programs for the Elckerlyc or other parts of Hmi
  • HmiResource: git repository for hmi specific data
  • HmiShared: git repository for 1) the ant build system setup, 2) binary (jar) releases of Hmi, 3) external jar libraries used within Hmi and Asap
  • (optional) realizertester: svn repository for our generic testing framework for realizers

Mirrors of all git repositories are maintained by both Hmi and CITEC.

CITEC repository info

Repositories are located at e.g., login with your CITEC username + pass. See for the repository list. Hendrik Buschmeier, Ramin Yaghoubzadeh or Herwin van Welbergen can give you access to the the soa repositories (see for contact info). Contact   Thilo Paul-Stueve if you need new repositories to be created; make sure to mention that they should be created within the Soa project.

Hmi repository info

Repositories are located at e.g., see for the full list of available repositories. Contact   Hendri Hondorp if you need access to Hmi git repositories and/or if you need new repositories to be created. You can use ssh keys to make your login easier (that is: requiring you to enter fewer or no passwords). To create a public/private key pair run


This creates a private key and a public key in the .ssh dir of your home directory. You then need to append the public key to the authorized_keys file in the .ssh dir of the home directory of the server (

cat >> ~/.ssh/authorized_keys

Make sure that the authorized_keys file is only accessible to the owner

chmod 600 ~/.ssh/authorized_keys

You should now be able to login (e.g. ssh without password, or using pass phrase you've set for your keys when creating them with ssh-keygen. If this fails, use ssh -v to troubleshoot. You can use multiple v-s (e.g. ssh -vv) to get more debug information.

realizertester repository

The realizertester is released at sourceforge: