DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41985>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41985 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Zip task changes the file |Zip task doesnt pick up the |attributes of entries when |read-only state of files |updating the archive |when adding ------- Additional Comments From [EMAIL PROTECTED] 2007-04-11 02:27 ------- Ok, I've changed the title of the bugrep again,to make it clear its about the RO bit. As Jeffrey says, we have been constrained by Java, pre-1.6. Permissions get lost on <zip>, <tar> and <copy>. More subtly, we are constrained by the need to be cross platform...you need builds that work on windows as well as unix, so can't rely on permission bits. Forcing people to use the <zipfileset> permissions does guarantee that the build file will work on windows, as well as unix. that said, as alexy notes, the read/read-only flag does appear to be more portable. File.setReadOnly() is java1.2+ and file.canWrite() is java1.0 era, so we should be able to propage the writeable flag. For java1.6+, we can even make a go at execute permissions, though I don't know what happens on Windows in that situation. Or -and this is the one that scares me- cygwin on windows. Because of that possibility, I'm leaving this open, instead of WONTFIX/CANTFIX. We may be able to do something about this, now. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
