manifestClassPath

manifestClassPath refers to the Class-Path attribute in a Java JAR manifest. The manifest is located at META-INF/MANIFEST.MF and can include a line such as Class-Path: lib/foo.jar lib/bar.jar. This attribute specifies additional JAR files that should be considered part of the runtime classpath when the JAR is executed as an application.

How it works: when you run a JAR with the java -jar command, the Java launcher reads the Class-Path entries from the manifest of the main JAR and augments the runtime classpath with the referenced JARs. Each entry is a space-separated path, typically relative to the location of the main JAR. These paths allow a distribution to bundle dependencies alongside the main artifact without embedding them inside the main JAR.

Limitations and scope: the Class-Path attribute is used only when launching with java -jar. If the application is started with a separate classpath (using -cp or -classpath) or by specifying a main class directly, the manifest’s Class-Path entries are ignored. Relative paths must resolve correctly at deployment time, and they are resolved against the location of the main JAR, not the current working directory. Long lists of dependencies can become unwieldy and error-prone.

Alternatives and practices: for complex deployments, developers often use build tools (such as Maven or Gradle) to produce shaded or fat jars, or to generate launcher scripts that assemble a precise classpath at runtime. Using the Class-Path attribute remains a lightweight option for simple dependency management within a distribution.