Versions Compared

Old Version 47

changes.mady.by.user Christian Vögele

Saved on

compared with

New Version Current

changes.mady.by.user Patrice Bouillet

Saved on

Key

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

...

Numberedheadings


Follow this guide carefully!

Install the correct JDK

It is essential, that you install the correct JDK. Currently the necessary is a openJDK version 1.7.0_51 - 1.7.0_80. Else you might encounter failing tests.

Find the JDK at:

Setup GitHub Account

The installation procedure needs a valid account to GitHub to download the repository. Check .

New Setup (automatic via Oomph)

The complete development environment can be arranged and configured by using the new Eclipse installation tool called "Oomph". It automates the installation and update of Eclipse development environments. Note that the first installation takes around 10-15 minutes depending on your internet connection. Any further installations are a matter of seconds.

Download Eclipse Installer - Oomph

Choose the corresponding Eclipse installer via the following links:

The Eclipse Installer might need a JDK version higher than 1.7.0_80. In this case you get an Error message when you start the Eclipse Installer. Then you have to use a higher JDK version during the installation process. Within the installation process you have to point to the necessary openJDK version given in above.

Executing installation

SourceForge Repository Error when using Oracle JDK

Fetching data from SourceForge repositories currently fails due to issues with their server's SSL handling when you run the installation using an Oracle JRE, subsequently causing the Eclipse installation to fail.
To resolve this, install the JCE Unlimited Strength Jurisdiction Policy Files before running the Eclipse Installer.
For more details on this issue see the discussion here.

The installation is done by copying the files to JDK/jre/lib/security overwriting the existing files.

After the download is finished, start Oomph and you will be greeted with the following:

OomphSimpleInstaller2.png

Select the options on the upper right and switch to the "Advanced Mode":

To continue the installation, you need to first select the appropriate product. For the inspectIT development environment, it is currently "Eclipse for RCP and RAP Developers" with running the version "Neon":

In the next screen, you need to add our inspectIT project. To do this, just press the + sign in the upper right and select GitHub projects Catalog with the following URL:

There should be now a new entry with "<User>->inspectIT" available. Double click on inspectIT to add it to this installation so that it will appear in the bottom table:

(Optional): If you want, there is another setup file which will download all additional test projects we currently use to verify that the features in inspectIT are still working. If you are interested in this, just additionally add the following setup URL:

 

The last screen before the installation begins lists all the variables you can change. Only the ones that are important to be changed will be described here (if you don't see some of them, check the "Show all variables" checkbox in the bottom part):

VariableDescription
Installation folder nameThis is the name of the root folder in which the workspace and the projects will be put into (in different sub-folders).
Root install folderThis is the path in which the installation folder name will be put into.
JRE 1.7 LocationThis should point to your OpenJDK 1.7 installation (See first step).
JRE 1.5 LocationIf you have a JRE 1.5 available, please put the location into this setting. This is needed for the Agent development as it must be compatible with 1.5. If you don't have one, you can always execute the Ant build of the Agent which will download a compatible 1.5 rt.jar and thus show errors if something is not working.
Author NameThis is used for the author JavaDoc label for new classes or if you append your name with auto-completion. Please change to your real name.

All there is left to do is to go to the final confirmation page and press Finish. Please wait now until the installation and configuration is complete.

Eclipse will be started and some tasks in Eclipse will be executed, thus wait for all background jobs to be completed!

Post-Installation Tasks

Mac OS X users

The Eclipse version for Mac is ignoring the project name property in the .project file. Thus the inspectit.root project will be named in Eclipse as inspectIT. This is most likely due to this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=337648

However, since other projects are linking to the inspectit.root project, the complete setup will not work and you might get a lot of warnings (check-style, linked resources, etc). The only solution for this is to change the name of the inspectIT/ folder (root of your Git repository) to inspectit.root/ and re-import all the projects. With this change you will have all the projects named correctly and there should be no change in any tracked file.

 

With the introduction of Gradle, 2 3 steps need to be manually executed after the oomph installer has finished:

  1. Select all java projects, right-click and execute "Gradle → Refresh All". What this does is basically executing a Gradle task named prodToLib which will prepare all the projects for the UI execution
  2. Execute the gradle task pdeBuild: Either through the command line as "./gradlew pdeBuild" or directly in the Eclipse UI through the Gradle Tasks Window.
  3. Open the inspectIT.target file, click on Reload, and set this as target platform.

The execution of the first step leads to several changes in the projects. Please revert them after you have executed the steps!

In case the ${project_loc:inspectit.root}/build/updatesite folder in the inspectIT.target file does not exist, execute "gradlew (gw) updateSite" in folder ${project_loc:inspectit.root}

 

Optional

  • Get  for Git

 

...