Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4294516

JDK 1.2 jar generate incorrect manifest file if used with -m option

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not an Issue
    • Icon: P2 P2
    • None
    • 1.2.2
    • tools
    • None
    • jar
    • unknown
    • generic

      To reproduce, create a dummy file called a.txt in your current directory
      from where you will invoke the jar command. you also need the manifest.txt
      file in the same directory (manifest.txt test case below):

      <path to jdk 1.1.8>/bin/jar cvmf manifest.txt test_1.1.8.jar a.txt

      <path to jdk 1.2.2>/bin/jar cvmf manifest.txt test_1.2.2.jar a.txt

      now you have two jar files, test_1.1.8.jar and test_1.2.2.jar.

      Next, extract the contents of these two jar files in different directories,
      so you will get the generated manifest files:

      1. mkdir 1.1.8
      2. copy test_1.1.8.jar to this directory.
      3. cd 1.1.8
      4. jar xvf test_1.1.8.jar
      5. vi META-INF/MANIFEST.MF

      you will find that manifest file looks like the manifest.1.1.
      Do similar steps for JDK 1.2.2 using test_1.2.2.jar file.

      Note the difference in generated MANIFEST.MF file below.

      % cat META-INF/MANIFEST.MF
      Manifest-Version: 1.0

      Name: a.txt
      PropertyOfA: TRUE
      Digest-Algorithms: SHA MD5
      SHA-Digest: wmfnlhOIaPWrba75W/V2+oZPgEE=
      MD5-Digest: 7RHv6kbIoQ/bspA7VR2c1Q==


      % cat META-INF/MANIFEST.MF
      Manifest-Version: 1.0
      Name: a.txt
      Created-By: 1.2.2 (Sun Microsystems Inc.)
      PropertyOfA: TRUE


      Here is the manifest.txt test case:

      % cat manifest.txt
      Name: a.txt
      PropertyOfA: TRUE

            zlisunw Zhenghua Li (Inactive)
            mchansunw Mei Chan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: