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=30438>. 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=30438 Import not working with relative paths and symlinks Summary: Import not working with relative paths and symlinks Product: Ant Version: 1.6.2 Platform: All OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] A build file at the top level (in directory .../acme/) delegates to another build file in src/lib2/ (.../acme/src/lib2), but src/ is a symlink to ../acme_src (which thus resolves to .../acme_src using getCanonicalPath). The build file in src/lib2/ imports ../../config/recurse.xml (.../acme/config/recurse.xml), but this fails, because apparently the basedir of src/lib2/build.xml was assigned after a getCanonicalPath() call. Note the symlink mimicks a ClearCase view with several vobs linked together. Both acme and acme_src are ClearCase vobs. On Linux, acme/src is a symlink to ../acme_src, but not on Windows, which is why I'd really like ../../config/recurse.xml to be found even when traversing symlinks. Is this a bug we can solve? I thought after Jesse's patch that this issue was resolved. Thanks, --DD PS: I'll attach a build file that sets up the environment, and a session log that demonstrates the step to reproduce the issue on a linux system. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
