ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15031] - ANT <copy> with <fileset> does not spot bad symlinks
Date Wed, 23 Jul 2003 18:03:43 GMT
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=15031>.
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=15031

ANT <copy> with <fileset> does not spot bad symlinks





------- Additional Comments From gus.heck@olin.edu  2003-07-23 18:03 -------
I think there is some possibility that JL may have a way to fix this, but more
consideration is needed. How does it react to things like named pipes and other
file system wierdos? Are these results true on all *nix's? What about across
different filesystems that may be mounted. And what about Cygwin?

JL, you might be interested to read bug 1550 for which I found a way to infer
the existance of Symlinks for the followsymlinks atribute. You will need to
answer the same types of questions before you can say that your method really
identifies broken symlinks only.

Even if it doesn't identify them specifically, it is possible that the other
things identified could be worth reporting with a warning, or even failing the
build.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message