• Page
• Discussion
• View source
• History
• Edit

From Eclipsepedia

Running an OT/J program basically requires three additional arguments to the JVM:

• the files otre.jar and org.apache.bcel_version.jar must be added to the classpath
• the file otre_min.jar must be added to the bootstrap classpath
• the file otre_agent.jar must be passed as a javaagent.

This is where these files can be found in an installation of the OTDT:

• OTDT ≤1.4.0:

plugins/org.objectteams.otdt_version/lib/

otre.jar

otre_min.jar

plugins/org.objectteams.runtime_version/

lib/

otre_agent.jar

otj/lib/jmangler/use/

BCEL.jar (note the old file name)

• OTDT ≥ 2.0.0:

plugins/org.eclipse.objectteams.otdt_version.jar!lib/ — unpack these nested jars to a location of your choice!

otre_agent.jar

otre_min.jar

plugins/

org.eclipse.objectteams.runtime_version.jar

org.apache.bcel_5.2.0.v201005080400.jar

Given that the paths to these files are set to variables OTRE, OTRE_MIN, OTRE_AGENT and BCEL, the following (Unix) command line can be used to launch an OT/J program:

 java -Xbootclasspath/a:${OTRE_MIN} -javaagent:${OTRE_AGENT} -classpath ${OTRE}:${BCEL}:other_classpath_entries fully.qualified.Main

If some teams should be instantiated and activated at launch time using the mechanism of OTJLD §5.5 the following argument is added to the command line:

 -Dot.teamconfig=config_file_name

where config_file_name refers to a text file listing the teams to activate.

See also

OTRE Parameters (controlling the behavior of the OTRE)