Skip to main content
Jump to: navigation, search

Difference between revisions of "OTHowtos/Running From Commandline"

(New page: Running an OT/J program basically requires three additional arguments to the JVM: * the files otre.jar and BCEL.jar must be added to the classpath * the file otre_min.jar must be added t...)
 
Line 29: Line 29:
 
   -Dot.teamconfig=''config_file_name''
 
   -Dot.teamconfig=''config_file_name''
 
where ''config_file_name'' refers to a text file listing the teams to activate.
 
where ''config_file_name'' refers to a text file listing the teams to activate.
 +
 +
[[Category:Object Teams|Running from Commandline]]

Revision as of 13:19, 4 March 2010

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

  • the files otre.jar and BCEL.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
  • OTDT 0.7.0 (incubation):
plugins/org.eclipse.objectteams.otdt_version/lib/
otre_agent.jar
otre_min.jar
BCEL.jar
plugins/org.eclipse.objectteams.runtime_version/lib/
otre.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.

Back to the top