I'm not sure if that is what you are after or not... but anyway...
We don't use relative paths, but instead we obtain the folder the ant file lives in, stick it in a property, and then prepend that to any path. The paths then become something like:
We end up with th convenience of relative paths and the ability to run scripts from different locations.
Hope that helps.
Thanks. That's what I ended up doing in the end. I also added (prior to that)
<property name="project.dir" value="."/>
So that it can be run without manually specifying project.dir. (project.dir will only be set to . if it is not already set by an outer script).
What I really wanted was for mxmlc to run relative to the ant task, eg.
Then each task inside the ant build file should run relative to "project". This is how <javac/> works. I don't think Adobe like relative paths though.
If you use
<property name="dir" location="../../whatever" />
That will create a path relative to the ant file... well, technically, it'll be relative to whatever the "basedir" setting in the <project> element is.