Sorry to be asking such an asinine question, but I can't make my
app run after I package it in a jar file, when my app refers to
library classes in a different jar file.

Code snippet:

package connectTest;

import com.sybase.jdbc2.jdbc.*;

public class ConnectTest {
 public ConnectTest() {
   try {
     DriverManager.registerDriver((Driver)
       Class.forName("com.sybase.jdbc2.jdbc.SybDriver")
       .newInstance());
   // etc...

I can make this test app work fine when I run it from Eclipse.
But when I package ConnectTest up into a jar file, it loses the
ability to find com.sybase.jdbc2.jdbc.SybDriver.  SybDriver.class
is in the jar file jconn2.jar.  I've copied both ConnectTest.jar
and jconn2.jar to c:\ (and used various other locations).  I've
done it with various settings of the classpath env variable (and
without classpath being set at all).  I know that the classpath
needs to point to the jar file itself, and not just the directory
containing the jar file. Here's an example command:

java -cp c:\;c:\jconn2.jar -jar ConnectTest.jar

If my manifest doesn't contain a Class-Path entry, eg:

Manifest-Version: 1.0
Main-Class: connectTest.ConnectTest

then the result of the above command is always a stack trace with:

java.lang.ClassNotFoundException: com.sybase.jdbc2.jdbc.SybDriver

Every time I tried setting a Class-Path line in the manifest, e.g.:

Manifest-Version: 1.0
Class-Path: c:/jconn2.jar c:/
Main-Class: connectTest.ConnectTest

(and I've tried about a dozen variations on the Class-Path line)

I get:

Exception in thread "main" java.lang.NoClassDefFoundError:
connectTest/ConnectTest

What am I missing?