[[archive(http://wiki.eclipse.org/OTRE_Parameters)]]
= Parameters controlling the behavior of the OTRE =

=== The following user-definable properties are interpreted by the OTRE ===

 * `ot.teamconfig`: passes a configuration file to the OTRE where globally active teams are listed (see [[otjld(5.5)]]). Also used by the OTDT to pass the list of teams from the Team Activation tab of a launch configuration (see [http://www.objectteams.org/distrib/documentation/guide/running.html#activation Team activation]).
    * value: path to config file
 * `ot.dump`: turns on dumping of transformed class files into directory `jplis_dump`.
 * `ot.log`: turns on (''verbose''!) logging to std out about activity of the transformers/weavers.
 * `ot.log.lift`: turns on std-out logging of any `LiftingVetoException` raised at runtime by generated dispatch code.
 * `ot.lifting.participant`: register a client class as a lifting participant (see #289).
    * value: fully qualified name of a class to act as a lifting participant
 * `ot.jpi`: enables highly experimental, unmaintained join point weaving

=== The following properties are passed from the IDE to the OTRE ===

 * `ot.debug`: turns on the generation of debug information in the byte code
 * `ot.debug.callin.stepping`: determines which parts of the dispatch code are exposed during step debugging, see [http://www.objectteams.org/distrib/documentation/guide/stepping.html#configure Configuring the callin stepping behavior].[[BR]]Possible values are a comma separated list of
    * `role` (''"Show pending dispatch to callin binding"'')
    * `recurse` (''"Show pending recursive dispatch"'')
    * `orig` (''"Show pending dispatch to original base method"'')
 * `ot.equinox`: tells the OTRE that it is running inside the Equinox framework.
 * `ot.equinox.dump`: this property controls the logging behavior of OT/Equinox and is respected by the OTRE regarding one particular log message (std err) (''"Warning: Repository could not lookup class ''className''!").