Skip to main content
Jump to: navigation, search

Difference between revisions of "OTEquinox/Config Ini"

(Mandatory declarations:)
Line 12: Line 12:
 
*<pre> osgi.classloader.lock=classname</pre>
 
*<pre> osgi.classloader.lock=classname</pre>
 
: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.  
 
: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.  
 
<ul><li>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 <code>eclipse.ini</code> (after -vmargs):<br>
 
<pre>-XX:+UnlockDiagnosticVMOptions
 
-XX:+UnsyncloadClass</pre></li></ul>
 
  
 
* <pre>ot.equinox=1</pre>
 
* <pre>ot.equinox=1</pre>
:This simple flag is needed to tell the OTRE that it runs inside OSGi.
+
:This simple flag is needed to tell the OTRE that it runs inside OSGi.
 
+
* <pre>osgi.splashPath=platform\:/base/plugins/org.objectteams.otdt</pre>
+
:This declaration tells the launcher to show the splash screen which has been customized for the OTDT. Note, that also eclipse.ini contains a similar declaration, where precedence between both declarations is not perfectly clear.  
+
  
 
==Optional application specific declarations==
 
==Optional application specific declarations==

Revision as of 11:53, 30 July 2012

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

Back to the top