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=28505>. 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=28505 [PATCH] File paths to imported build files should not be canonicalized ------- Additional Comments From [EMAIL PROTECTED] 2004-04-26 19:45 ------- In such a case you could make the symlink to /a/scripts, not /a/scripts/b, and <import file="/usr/home/peter/a_scripts/b/import.xml"/> Clearly in this case /a/scripts is intended to be a whole (you cannot use the b subdir on its own), so linking to just a part of it sounds dubious to me. I realize that there are cases where having the canonical path would be handy, but is it worth the (possibly unsolvable) problems for those people who *don't* want the canonical path? Other Ant tasks (in particular, <property>) don't magically traverse symlinks or otherwise canonicalize file paths. Maybe better to have an explicit task to canonicalize a file path and store the result in a new property, if that's really what you want. Or perhaps an extra attribute 'canonicalize' on <import> (default should be false, IMHO). BTW import.html in the manual still states "Important: We have not finalized how relative file references will be resolved in deep/complex build hierarchies -such as what happens when an imported file imports another file. Use absolute references for enhanced build file stability, especially in the imported files." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
