You don't have to use ALL jar files that you downloaded. There is a structure to it...
If your including both server and client APIs in the same JVM then you need
maverick-legacy-server-no-common-<version>.jar
maverick-legacy-client-no-common-<version>.jar
maverick-common-<version>.jar
Then from lib you need at least the following jar files
oro-<version>.jar
slf4j-api-<version>.jar
jzlib-<version>.jar
If you need to enable logging then you should use the Log4J provider
slf4j-log4j-<version>.jar
log4j-<version>.jar
We also recommend BouncyCastle JCE and PKIX to ensure the maximum security for your application. These are optional.
bcprov-<version>.jar
bcpkix-<version>.jar
The following are optional features from /opt and their dependencies. If you don't use these features then you don't need the libs.
-- Using VirtualFileFactory in the server API --
ehcache-<version>.jar
-- Using VFSFileFactory in the server API --
commons-vfs2-<version>.jar
commons-logging-<version>.jar
-- Using VirtualShell to provide a bash type session--
sshd-virtualshell-<version>.jar
commons-configuration-<version>.jar
commons-cli-<version>.jar
commons-logging-<version>.jar
commons-collections-<version>.jar
commons-lang-<version>.jar
commons-digester-<version>.jar
commons-beanutils-<version>.jar
bsh-<version>.jar
-- Using NativeShell to provide access to a native shell --
sshd-nativeshell-<version>.jar
-- Maverick Agent for agent authentication--
maverick-agent-<version>.jar
(If you want Unix Socket support)
junixsocket-*
native-lib-loader-<version>.jar
-- SFTP provider for Commons VFS that uses the client API --
maverick-vfs-ssh-<version>.jar
commons-logging-<version>.jar
commons-vfs2-<version>.jar
