DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14320>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14320 copy fileset followsymlinks="false" does not copy symlinks at all ------- Additional Comments From [EMAIL PROTECTED] 2002-11-07 15:57 ------- Hehe you don't need to sell me on the value of platform specific tasks. I wrote the Symlink task (committed to 1.6 alpha yesterday) and have also written a chgrp and chown which should get commited soon. I might at some point work on symlink support within the copy task, but first I intend to expand my symlink task so that the user can provide information that answers the question "relative to what directory?", and get a relative link. You do make a reasonable point about clarifying the effects of followSymlinks. in retrospect a slightly better name might have been ignoreSymlinks (with oposite atribute values of course), but the perspective at the time was that of delete task rampaging through unintended sections of the file system. To take another perspective, FileSets are collections of files, and symlinks really arn't the same as files, so the current behavior is not inconsistant with that idea. The problem comes in that people tend to think of anything in te filesystem as a file. (which is a very nice way to think when it works). I am also given to wonder what java (and therefore ant) does if it selects a named pipe, or other funky unix fs object. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
