KIELER Project


Get me back to the home page!

Page tree

Versions Compared

Old Version 43

changes.mady.by.user Alexander Schulz-Rosengarten

Saved on

compared with

New Version 44

changes.mady.by.user Alexander Schulz-Rosengarten

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

By default, the Oomph setup will import every project and setup the working sets just like cds likes them. Because he created the setup and likes to abuse his power. Anyway, you can choose not to import projects and setup working sets by selecting a different project stream.

 

  • Oomph now asks you to enter some more information. You can usually leave the settings as is, except for the Installation folder name. This will be the directory under which all your Eclipse installations installed with Oomph will appear, each in a separate sub-directory. Select a proper directory and click Next.

    • Expand
    titleClick here to expand the installation guide...
    1. Go to this site and download the Eclipse Installer for your platform. The site does not advertise that it ships the Oomph Eclipse Installer but downloading Eclipse with the orange download button will give you the installer.
    2. Start the installer. You should see something like this:

      Click the Hamburger button at the top right corner and select Advanced Mode. Why? Because we're computer scientists, that's why!
    3. Oomph now wants you to select which Eclipse distribution you want to use to develop KIELER in. Select the Eclipse Platform and click Next.

    4. Next, we need to tell Oomph how to get everything setup an Eclipse ready for KIELER development. Download our Oomph setup file (simply save the file as kieler.setup if your download manager wants to download a kieler.xml), click the Plus button at the top right corner and add the setup file to the Eclipse Projects catalog. Double-click the new KIELER Click the Plus button at the top right corner. Select Eclipse Projects as Catalog and insert the following setup URL into the Resource URI field, then press OK.

      Pragmatics Developers:https://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/config/browse/setups/kieler-pragmatics-developers.setup?raw
      Semantics Developers:https://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/config/browse/setups/kieler-semantics-developers.setup?raw
      Info
      titleObsolete Setups

      In an earlier version of this site, you might be instructed to download a KIELER setup file and register the local file path. This setup file is now obsolete. Please do not use it anymore. You might also want to remove it from the list and delete the downloaded setup file but this will cause errors in all Eclipse installations created with this setup file. So be careful and don't force me to say: I told you so!

    5. Now Oomph lists the corresponding setup in the <User> folder. Double-click on the new KIELER Pragmatics/Semantics entry. This will cause an item to appear in the table at the bottom of the window. The Stream column entry can be edited to choose which part of KIELER on which state/branch you want to work on (e. g. pragmatics or semantics). Once you're done, click Next.

    Info
    titleI Don't Want To Import Everything
    Info
    titleBut... I Already Have Git Repositories

    By default, the Oomph setup will clone all required Git repositories for each Eclipse installation, which takes up disk space and results in unnecessary duplication. You can change that by changing the Git clone location rule to Located in the specified absolute folder location and then setting the locations for each cloned repository accordingly.

    Oomph will clone the repositories into the given folder, or use existing repositories.

    Info
    titleSeparate Installations?
    This is the part that veteran Eclipse developers will find strange. In the Oomph world, there is no one big Eclipse installation anymore. Instead, we simply use one installation for each project we're working on, completely self-contained in a folder that also contains the workspace and all required Git repositories. If something goes wrong, simply delete the whole folder and install a new Eclipse using Oomph.
    Having multiple Eclipse installations isn't even a problem in terms of disk space. Each installation is very lightweight, because all features and plug-ins used are saved in a centralized bundle pool (usually something like ~/.p2), which keeps each installation very small.
  • Oomph now displays a summary of what will happen once you click Finish. Ignore it and click Finish.
  • Once the basic installation is complete, your new Eclipse will start (at this point, you can safely close the Oomph dialog). Now, Oomph will try (and probably fail) to clone all required Git repositories. The Eclipse window will look something like this (once you've closed the Welcome page):

    Note the icon at the bottom with the error marker. It tells you that something went wrong during the Oomph setup.
  • The problem is that Eclipse doesn't know which SSH key to use to clone the repositories. Go to the Eclipse preferences and navigate to General -> Network Connections -> SSH2. Add the private key you want to use to connect to our repositories and click OK.
  • You will now need to retry the failed Oomph setup steps. Either click on the Oomph setup icon at the bottom of the Eclipse window (if it's still there), or select Perform Setup Tasks from the Help menu. The dialog shows the failed setup tasks. Click Back, Next, and Finish to retry them all.

    • ...