Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OTEquinox/Config Ini"
Line 27: | Line 27: | ||
See [[OTEquinox/Forced Export|Forced Export]] | See [[OTEquinox/Forced Export|Forced Export]] | ||
− | [[Category:OTEquinox]] | + | [[Category:OTEquinox|Config Ini]] |
Revision as of 09:36, 27 February 2010
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.
- 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
-
ot.equinox=1
- This simple flag is needed to tell the OTRE that it runs inside OSGi.
-
osgi.splashPath=platform\:/base/plugins/org.objectteams.otdt
- 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
See Forced Export