- Goals
 - User guide
- History
 - Application testing list
 - Getting Started
 - Hardware Compatibility List
 - Hardware requirements
 - JNode Commands
- acpi
 - alias
 - arp
 - basename
 - beep
 - bindkeys
 - bootp
 - bsh
 - bzip2
 - cat
 - cd
 - class
 - classpath
 - clear
 - compile
 - console
 - cpuid
 - date
 - del
 - device
 - df
 - dhcp
 - dir
 - dirname
 - disasm
 - echo
 - edit
 - eject
 - env
 - exit
 - gc
 - grep
 - gzip
 - halt
 - help
 - hexdump
 - history
 - ifconfig
 - java
 - kdb
 - leed, levi
 - loadkeys
 - locale
 - log4j
 - ls
 - lsirq
 - man
 - memory
 - mkdir
 - mount
 - namespace
 - netstat
 - onheap
 - page
 - ping
 - plugin
 - propset
 - pwd
 - ramdisk
 - reboot
 - remoteout
 - resolver
 - route
 - rpcinfo
 - run
 - startawt
 - syntax
 - tar
 - tcpinout
 - thread
 - time
 - touch
 - unzip
 - utest
 - vminfo
 - wc
 - zip
 
 - JNode GUI
 - JNode Shell
 - Performance
 - Status
 
 - Classlib developers guide
 - Developer guide
 - Tester guide
 - Porting guide
 - Blogs
 - Project development
 - Glossary
 - Proposals
 - FAQ
 - Papers & presentations
 - References
 - Research
 
classpath
classpath
| Synopsis | ||
| classpath | prints the current classpath | |
| classpath | <url> | adds the supplied url to the end of the classpath | 
| classpath | --clear | clears the classpath | 
| classpath | --refresh | cause classes loaded from the classpath to be reloaded on next use | 
| 
Details | ||
| 
The classpath command controls the path that the command shell uses to locate commands to be loaded.  By default, the shell loads classes from the currently loaded plug-ins.  If the shell's classpath is non-empty, the urls on the path are searched ahead of the plug-ins.  Each shell instance has its own classpath.
 If the <url> argument ends with a '/', it will be interpreted as a base directory that may contain classes and resources. Otherwise, the argument is interpreted as the path for a JAR file. While "file:" URLs are the norm, protocols like "ftp:" and "http:" should also work.  | 
||