[Bug 54762] New: Java 5 fails to run jar file with manifest attribute used

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54762

            Bug ID: 54762
           Summary: Java 5 fails to run jar file with manifest attribute
                    used
           Product: Ant
           Version: 1.9.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Core tasks
          Assignee: notifications@ant.apache.org
          Reporter: initialzero@gmail.com
    Classification: Unclassified

Created attachment 30113
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=30113&action=edit
Use Java 5 to run this ant file for a demonstration

Using ant 1.9.0 jar Java 5 fails to execute a jar file with the manifest
attribute. Note: The generated jar works with Java 6 and 7.

The problem is demonstrated when the manifest attribute is used with the jar
task.

I have attached a sample ant build.xml file to be used with Java 5 to view the
failure.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54762] Java 5 fails to run jar file with manifest attribute used

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54762

Stefan Bodewig <bo...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |1.9.1

--- Comment #5 from Stefan Bodewig <bo...@apache.org> ---
seems to be fixed with svn revision 1462911

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54762] Java 5 fails to run jar file with manifest attribute used

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54762

--- Comment #1 from initialzero@gmail.com ---
The output using Java 5 is "Invalid or corrupt jarfile"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54762] Java 5 fails to run jar file with manifest attribute used

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54762

--- Comment #3 from Stefan Bodewig <bo...@apache.org> ---
I have created AntUnit tests from your example - ine using a separate file and
ine using a nested manifest - we'll see how they fare on our build matrix.

I've compared the created jars byte by byte and the only difference is the
timestamps.  Right now I suspect Java5 cannot deal with the Zip64 extra field
Ant 1.9 now adds, but then it should fail with nested manifest elements as
well.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54762] Java 5 fails to run jar file with manifest attribute used

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54762

--- Comment #2 from Stefan Bodewig <bo...@apache.org> ---
In addition you said on the mailing list, the problem went away if you used a
nested manifest element inside the jar task instead, right?

I'll look into it but may need your help testing it since I don't have any
Java5 around anymore.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54762] Java 5 fails to run jar file with manifest attribute used

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54762

--- Comment #4 from Stefan Bodewig <bo...@apache.org> ---
OK, both testcases fail in Jenkins, I'll add an option to completely turn of
zip64 extensions and make turn it on in <jar> by default.

-- 
You are receiving this mail because:
You are the assignee for the bug.