arthur.frechette@East 1998-02-06
A blank line in the manifest file between manifest attribute entries caused
the manifest file to not be interpreted or parsed correctly thereby causing
the program to fail loading classes properly.
:::::::::::
manifest.mf
:::::::::::
Manifest-Version: 1.0
Main-Class: T0
Class-Path: ../../ext/e1/e1.jar ../../ext/e2/e2.jar
or
:::::::::::
manifest.mf
:::::::::::
Manifest-Version: 1.0
Main-Class: T0
Class-Path: ../../ext/e1/e1.jar ../../ext/e2/e2.jar
or
:::::::::::
manifest.mf
:::::::::::
Manifest-Version: 1.0
Main-Class: T0
Class-Path: ../../ext/e1/e1.jar ../../ext/e2/e2.jar
causes this
adfsys 2847 =>make run
java -classpath /js/files/JDK1.2_latest/solaris/lib/classes.zip:../.. sun.misc.Launcher -verbose -jar T0.jar
Could not open JAR file: T0.jar
*** Error code 1
make: Fatal error: Command failed for target `run'
The manifest below is the only one that works.
:::::::::::
manifest.mf
:::::::::::
Manifest-Version: 1.0
Main-Class: T0
Class-Path: ../../ext/e1/e1.jar ../../ext/e2/e2.jar
No blank line between attribute entries.
- duplicates
-
JDK-4181908 KeyLabs: class not found error generated when using the attached jar file
-
- Closed
-
- relates to
-
JDK-4170552 Manifest files fail to compile with jdk1.2 if a tab character is leading char
-
- Closed
-
-
JDK-4186895 Certain forms of manifest are rejected by 1,2, but accepted by 1.1
-
- Closed
-