IDE for OSGi and project setups

This page describes the process of consuming the projects provided by the OSGi Alliance from their Github site.

It consists of 2 phased process, which involves interactions on the website and on your local machine.

Setup local IDE for the creation of a PR - PullRequest

Probably you have got an anwser from Peter Kriens including an invitation for a PR. Then this process describes how to accept this invitation ;-)

  1. GitHub: create a fork of a project
  2. local: execute the engage[.sh|.cmd]
  3. local: select IDE for OSGi product and project you forked on GitHub
  4. local: edit the project inside the IDE instance and commit your changes to your GitHub fork
  5. GitHub: create pull request for the changes you made



open a terminal/shell create a installation directory <instDir> e.g. mkdir ~/<instDir>


  • copy the following line and execute it inside <instDir>
  • IDE and Project selection

    1. on the top-right folder icon mark the OSGi products [required only after initial installation]
    2. select from the section at the bottomOSGi products the product you want to install e.g. IDEfix for OSGi Mars and press Next
    3. on the top-right folder icon mark the OSGi projects [required only after initial installation]
    4. scroll down to OSGi projects and check the projects you want to work e.g. on and press Next
    5. configure the variables and press Next
    6. review the tasks and if satisfied press Finish
    7. Press "Accept" in the appearing "Licenses" pop-up window
    8. Eclipse IDE should appear with the "Bndtools - Eclipse" perspective open.
    9. Eclipse Installer can be closed now and IDE with your project is ready.

    Subsequent Startups of installed IDE for OSGi

    Subsequent Startups of eclipseInstaller


    the installation creates (additionally to the <installDir> folder) following directories (~ means %USERPROFILE% on windows)

    1. ~/.eclipse/org.eclipse.oomph.* containing the oomph preferences and user-specified variables
    2. ~/.p2 containing the shared bundle pool for all oomph installations