Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OTHowtos/Running From Commandline"
< OTHowtos
| Line 1: | Line 1: | ||
Running an OT/J program basically requires three additional arguments to the JVM: | Running an OT/J program basically requires three additional arguments to the JVM: | ||
| − | * the files otre.jar and | + | * 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_min.jar must be added to the bootstrap classpath | ||
* the file otre_agent.jar must be passed as a javaagent. | * the file otre_agent.jar must be passed as a javaagent. | ||
| Line 13: | Line 13: | ||
:::<code>otre_agent.jar</code> | :::<code>otre_agent.jar</code> | ||
::otj/lib/jmangler/use/ | ::otj/lib/jmangler/use/ | ||
| − | :::<code>BCEL.jar</code> | + | :::<code>BCEL.jar</code> ''(note the old file name)'' |
*'''OTDT 0.7.0 (incubation):''' | *'''OTDT 0.7.0 (incubation):''' | ||
| Line 19: | Line 19: | ||
::<code>otre_agent.jar</code> | ::<code>otre_agent.jar</code> | ||
::<code>otre_min.jar</code> | ::<code>otre_min.jar</code> | ||
| − | |||
:plugins/org.eclipse.objectteams.runtime_''version''/lib/ | :plugins/org.eclipse.objectteams.runtime_''version''/lib/ | ||
::<code>otre.jar</code> | ::<code>otre.jar</code> | ||
| + | :plugins/ | ||
| + | ::<code>org.apache.bcel_5.2.0.v201005080400.jar</code> | ||
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: | 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: | ||
Revision as of 06:22, 11 June 2010
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.jarotre_min.jar
- plugins/org.objectteams.runtime_version/
- lib/
otre_agent.jar
- otj/lib/jmangler/use/
BCEL.jar(note the old file name)
- lib/
- OTDT 0.7.0 (incubation):
- plugins/org.eclipse.objectteams.otdt_version/lib/
otre_agent.jarotre_min.jar
- plugins/org.eclipse.objectteams.runtime_version/lib/
otre.jar
- plugins/
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.