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=40129>. 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=40129 Summary: Wrong path calculation in <copy> when basedir set from command line Product: Ant Version: 1.6.5 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Core AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] When one uses a the -D switch on the command line to set the basedir property from outside, then relative paths are calculated differently from when basedir is simply assumed as "." This behaviour only occurs when the path is prepended by ${basedir}. The paths are set by properties used in a fileset. Please see the little "test case" attached. It is a small directory structure: updir-test updir-test/res updir-test/build updir-test/build/node There are two short build.xml files in the uppermost and the lowest dir. They are identical (upper is symlink, actually). Both scripts are supposed to have build/node as basedir, but one lies two levels higher and gets the -Dbasedir=build/node argument. So I suppose they should behave the same, but the one with cl argument fails. The test.sh script makes those calls as a test. (Test was run under Linux.) -- 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]
