Versions Compared

Old Version 16

changes.mady.by.user Christoph Heger

Saved on

compared with

New Version Current

changes.mady.by.user Ivan Senic

Saved on

Key

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

...

All the OSGi bundles we retrieve via Ivy will be placed in the ${project_loc}/lib/osgi inspectit.root/build/updatesite folder. However, when an Eclipse plug-in is run from the Development environment, we need to have those plug-ins available in the Eclipse/plugins/ folder. Since it is complicated for developer to constantly update the plugin folder of Eclipse installation manually, we have created the Target Definition for inspectIT RCP where all needed plug-ins are defined. 

The definition file is inspectit.root/resources/target/inspectIT.target and defines four places as the source of required plug-ins for execution:

...

  1. inspectit.root/libbuild/osgi folderupdatesite
  2. Eclipse Indigo update site with plug-ins defined for Eclipse platform and Eclipse Platform SDK located under inspectit.root/build/eclipse
Everything a developer has to do is to set the inspectIT Main Target as target platform. This can be done by opening the inspectIT.target and click on the Set as Target Platform link in the top right corner of the Target definition. Please make sure to perform Ivy > Retrieve on all three plug-in projects so that depending /lib/osgi folders can be used properly.

Support for Java 1.8

Since Eclipse Indigo does not support Java 1.8, we have manually added JavaSE-1.8 profile to the needed jar (described https://stackoverflow.com/questions/24669940/java-8-missing-required-capability-require-capability-osgi-ee-filter-osg) and updated the patched Eclipse base to the Nexus under version 3.8.2_20170531. This is why target definition must point to the updated base and the update site for the Eclipse Indigo can not be used.