/usr/share/doc/stilts/sun256/jvmClasspath.html is in stilts-doc 3.1.2-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>Class Path</title>
</head>
<body>
<hr>
<a href="jvmArgs.html">Next</a> <a href="invoke.html">Previous</a> <a href="invoke.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="jvmArgs.html">Java Flags</a><br>
<b>Up: </b><a href="invoke.html">Invocation</a><br>
<b>Previous: </b><a href="invoke.html">Invocation</a><br>
<hr>
<h3><a name="jvmClasspath">3.1 Class Path</a></h3>
<p>The classpath is the list of places that Java looks to find
the bits of compiled code that it uses to run an application.
Depending on how you have done your installation the core STILTS
classes could be in various places, but they are probably in a
file with one of the names
<code>stilts.jar</code>,
<code>topcat-lite.jar</code> or
<code>topcat-full.jar</code>.
The full pathname of one of these files can therefore be used as
your classpath. In some cases these files are self-contained and
in some cases they reference other jar files in the filesystem -
this means that they may or may not continue to work if you
move them from their original location.
</p>
<p>Under certain circumstances the tools might need additional classes,
for instance:
<ul>
<li>JDBC drivers (see <a href="jdbcConfig.html">Section 3.4</a>)
</li>
<li>Providing extended algebraic functions
(see <a href="jelExtend.html">Section 10.7.3</a>)
</li>
<li>Installing I/O handlers for new table formats
(see <a href="http://www.starlink.ac.uk/stil/sun252/pluggableIO.html">SUN/252</a>)
</li>
</ul>
In this case the classpath must contain a list of all the jar files in which
the required classes can be found, separated by colons (unix) or
semicolons (MS Windows). Note that even if all your jar files
are in a single directory you can't use the name of
that directory as a class path - you must name each jar file,
separated by colons/semicolons.
</p>
<hr><a href="jvmArgs.html">Next</a> <a href="invoke.html">Previous</a> <a href="invoke.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="jvmArgs.html">Java Flags</a><br>
<b>Up: </b><a href="invoke.html">Invocation</a><br>
<b>Previous: </b><a href="invoke.html">Invocation</a><br>
<hr><i>STILTS - Starlink Tables Infrastructure Library Tool Set<br>Starlink User Note256<br>STILTS web page:
<a href="http://www.starlink.ac.uk/stilts/">http://www.starlink.ac.uk/stilts/</a><br>Author email:
<a href="mailto:m.b.taylor@bristol.ac.uk">m.b.taylor@bristol.ac.uk</a><br>Mailing list:
<a href="mailto:topcat-user@jiscmail.ac.uk">topcat-user@jiscmail.ac.uk</a><br></i></body>
</html>
|