Run class in Jar file

Invoking from a different directory

If your current directory isn't the same as your JAR's location, double-check your classpath:

• On Unix/Linux:

  java -cp /absolute/path/to/YourApp.jar com.package.ClassWithMain // Just like groceries, path matters! 🛒
  

• In a Windows setup:

  java -cp C:\absolute\path\to\YourApp.jar com.package.ClassWithMain // Don't forget Windows loves backslashes ❤️!
  

Always replace /absolute/path/to/ or C:\absolute\path\to\ with your JAR file location's actual path.

Naming conventions are here to help

Adhere to naming conventions: classes are happier in distinct packages, not in the default one. This prevents potential mess-up when loading classes in different environments. Also, the names of your classes should ideally not overlap with Java's standard library or other common libraries. Good naming will save your day!

System properties and common pitfalls

The -D option allows you to inject system properties:

java -Dcolor=blue -cp YourApp.jar com.package.ClassWithMain // I always thought Java liked blue color 😉


For error hunting, inspect class and JAR names for typos, and verify your JAR's manifest has Main-Class configured properly.

Using manifest for executable JARs

Building an executable JAR needs a manifest file with the entry: Main-Class. When your manifest plays ball, the -jar flag makes your program execution a breeze:

java -jar ExecutableApp.jar // "Look, Ma, no `-cp` here!" 😎


Verify the manifest's Main-Class to assure smooth execution.

Advanced classpath setting

With complex classpath requirements, specifying multiple JARs or directories is common. Use path separator (':' for Unix/Linux and ';' for Windows) appropriately:

java -cp "lib/*;YourApp.jar" com.package.ClassWithMain // The '*' is not making a wish here, it's setting your classpath right! 😜


Opting for different classpath notations

You can replace -cp with -classpath. It's all about comfort with your shell environment or personal style:

java -classpath YourApp.jar com.package.ClassWithMain // With `classpath` or without, you're still a class programmer!


Debugging classpath with verbose option

If there are issues like missing or misconfigured Main-Class, typographical errors, or incorrect classpath, then -verbose:class is your detective:

java -verbose:class -cp YourApp.jar com.package.ClassWithMain // This won't make you a class clown if you use it! 🤡
