The ZKM Script
classpath statement sets the classpath that will be used by Zelix KlassMaster.
Zelix KlassMaster uses its classpath to find all classes:
Note that Zelix KlassMaster will look inside of any archives appearing in your
- directly or indirectly extended or implemented by the classes you have opened,
- that are specified in the signatures of any methods in the classes you have opened.
classpath statement and recursively add any embedded archives to the effective classpath.
So, if you have an archive myJar.jar in your
classpath statement which contains another archive named embedded.jar then both myJar.jar and embedded.jar will be in the effective classpath.
Note also that the classes you have opened within Zelix KlassMaster do not have to appear in its classpath.
Also, the Java bootstrap classes should appear in whatever classpath you set.
If your classes were compiled using the JDK 1.1 then the path to the JDK 1.1
classes.zip must appear in your classpath.
If you used the JDK 1.2 or better then the path to corresponding
rt.jar should appear in your classpath.
If you do not specify a path to any bootstrap classes then Zelix KlassMaster will automatically append the path to the bootstrap
classes associated with the JVM you are using to run Zelix KlassMaster.
In the absence of a
classpath statement the classpath with which Zelix KlassMaster was started
will be used.
In the Windows or OS/2 environments
In a Unix environments (including Mac OS X)
As shown above, you can break the classpath up into independent, quoted Strings without using ";" or ":" separators.
This syntax is platform independent and is recommended.
"classpath" ("\"" classpathString "\"")+ ";"
classpathString ::= path (pathSeparator path)*
path is a file system path specifying a folder or archive file and
pathSeparator is the character returned by
System.getProperty("path.separator") by the JVM running Zelix KlassMaster.
path can contain the
"*" wildcard in its final qualifier.