Frankly, I don't know, and don't care, since there's no point in using such
absolute pathnames, especially for basedir. I want my build files to be
location-independent, meaning that I can drop my acme example in any
directory, C:\, X:\whatever, etc... and it continues to work. That way, when
I checkout a new CVS sandbox for a branch or specific version of a project,
it works there without modifications at all. If you depend on stuff external
to your project, then you must use absolute pathname, in properties files,
or in the environment (accessed using <property environment="env" /> and
${env.MY_ENV}).If your questions below really matter to you (as they seem to), then dive in, and examine the source code. I don't personally see the point, but that's just me. --DD -----Original Message----- From: Daniel Barclay [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 4:17 PM To: Ant Users List Subject: RE: How do I specify multiple Windows directories in one <propert y name> statement? > ...these two paths are relative to the project's > 'basedir' attribute, itself being relative to the actual > location in the filesystem of the build.xml file ant parses. If the basedir is specified as "C:\a", and some filename that is to be evaluated relative to the basedir is specified as "D:\b", that filename refers to "D:\b", right? If, instead, the filename is specified as "\b", then it refers to "C:\b", right? Daniel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
