arthur.frechette@East 1998-05-11

JDK Tested: java full version "JDK-1.2beta4-E"

A test regression was introduced concerning JAR files and manifest files.
None of the jars are being built properly due to the following error:

make jars
echo "Creating JAR file (e1.jar) ..."
Creating JAR file (e1.jar) ...
jar cvfm e1.jar manifest.e1 pkgs
java.io.IOException: invalid header field
        at java.lang.Throwable.<init>(Compiled Code)
        at java.util.jar.Attributes.read(Compiled Code)
        at java.util.jar.Manifest.read(Compiled Code)
        at java.util.jar.Manifest.<init>(Manifest.java:55)
        at sun.tools.jar.Main.run(Main.java:88)
        at sun.tools.jar.Main.main(Main.java:667)
make: Error code 1
make: '../../ext/e1/e1.jar' removed.


After initial investigation it is determined that the cause of the failure is
a result of having a <TAB> instead of a <SPACE> after the ":" between the
attribute name and the attribute value. This appears to be a bug since this
used to work before with no problems. Also a <TAB> should be considered white
space just like a <SPACE> and the parser should properly parse this. This
would be a big restriction to customers creating manifest files to make sure
they have to put a <SPACE> there as opposed to a <TAB>.

The following is an example of the manifest file used. Removing the <TAB>
between the ":" and the attribute value caused the JAR to be built fine.
This is a BUG since a <SPACE> or <TAB> should be allowed and is white space.


Manifest-Version: 1.0
Sealed: false

Name: pkgs/one/
Sealed: true