http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1313
*** shadow/1313 Wed Apr 11 13:09:18 2001 --- shadow/1313.tmp.12085 Wed May 2 14:34:07 2001 *************** *** 5,17 **** | Status: NEW Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Linux | ! | Priority: Component: Core tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | - | CC list: Cc: | +----------------------------------------------------------------------------+ ! | URL: | +============================================================================+ | DESCRIPTION | Ant generates a zip file from a the task --- 5,16 ---- | Status: NEW Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Linux | ! | Priority: High Component: Core tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | +----------------------------------------------------------------------------+ ! | URL: http://developer.java.sun.com/developer/bugParade/bugs/40975 | +============================================================================+ | DESCRIPTION | Ant generates a zip file from a the task *************** *** 20,23 **** but under Linux, when this zip file is decompressed it doesn't make the directories executable so the average user cannot "cd" to that ! directory. --- 19,30 ---- but under Linux, when this zip file is decompressed it doesn't make the directories executable so the average user cannot "cd" to that ! directory. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-05-02 14:34 ------- ! I noticed that bodewig made modifications to the zip/jar/war/ear tasks to use ! his own implementation of the ZipOutputStream class. This problem seems to be ! with the JDK itself, not Ant. Any changes made to JDK could cause Ant's ! implementation to need reworked. ! See Java bug ID 4097578 in for a more descriptive example of this problem and a ! workaround of setting the umask before extracting the jar file.
