Difference between revisions of "OTEquinox/Config Ini"

Latest revision as of 14:26, 17 August 2014

OTDT ≤ 2.2
This page is relevant for OTDT version ≤ 2.2.
Starting with version 2.3 no more changes are required in config.ini

OT-Specific Declarations in config.ini

The file configuration/config.ini contains fundamental settings for an OSGi installation. OT/Equinox adds a few additional declarations to this file, which are described here.

Mandatory declarations:

Adding mandatory declarations to the file config.ini is done through the "touchpoint" mechanism of the p2 provisioning system, so everything happens automatically while installing the OTDT. This section only gives background for those who want to know what's going on behind the scenes.

• osgi.hook.configurators.include=org.objectteams.eclipse.transformer.hook.HookConfigurator
  osgi.framework.extensions=org.objectteams.eclipse.transformer.hook

  
  These two declarations announce the OT/J bytecode transformers to the OSGi framework, by using the hooks described in Adaptor Hooks.

•  osgi.classloader.lock=classname

This line is also recommended in order to tell the framework to use a new locking strategy for all classloaders, which is known to work best for OT/Equinox.

• ot.equinox=1

This simple flag is needed to tell the OTRE that it runs inside OSGi.

Optional application specific declarations

See Forced Export

OT-Specific Declarations in eclipse.ini

Due to the top voted bug reported against the Sun JVM (see https://bugs.eclipse.org/121737) additionally two vendor-specific options need to be passed to the JVM (not on MacOS, where these options would cause the VM to crash), which happens by the following entries in eclipse.ini (after -vmargs):

-XX:+UnlockDiagnosticVMOptions
-XX:+UnsyncloadClass

When running on Java 7 or greater these options should no longer be needed.