background image
<< sysinfo example | Using dblook >>

Using sysinfo to check the classpath

<< sysinfo example | Using dblook >>
Derby Tools and Utilities Guide
58
Found support for locale: [it]
version: 10.8.0.0 - (1076370)
Found support for locale: [ja_JP]
version: 10.8.0.0 - (1076370)
Found support for locale: [ko_KR]
version: 10.8.0.0 - (1076370)
Found support for locale: [pl]
version: 10.8.0.0 - (1076370)
Found support for locale: [pt_BR]
version: 10.8.0.0 - (1076370)
Found support for locale: [ru]
version: 10.8.0.0 - (1076370)
Found support for locale: [zh_CN]
version: 10.8.0.0 - (1076370)
Found support for locale: [zh_TW]
version: 10.8.0.0 - (1076370)
------------------------------------------------------
When you request help for a problem by posting to the derby-user mailing list, include a
copy of the information provided by the
sysinfo
utility.
Using sysinfo to check the classpath
sysinfo provides an argument (-cp) which can be used to test the classpath.
java org.apache.derby.tools.sysinfo -cp
[ [ embedded ][ server ][ client] [ tools ] [ anyClass.class ] ]
If your environment is set up correctly, the utility shows output indicating success.
You can provide optional arguments with -cp to test different environments. Optional
arguments to -cp are:
· embedded
· server
· client
· tools
· classname.class
If something is missing from your classpath, the utility indicates what is missing. For
example, if you neglected to include the directory containing the class named SimpleApp
to your classpath, the utility would indicate this when the following command line was
issued (type all on one line):
$ java org.apache.derby.tools.sysinfo -cp embedded SimpleApp.class
FOUND IN CLASS PATH:
Derby embedded engine library (derby.jar)
NOT FOUND IN CLASS PATH:
user-specified class (SimpleApp)
(SimpleApp not found.)