Hello all,
I am in a situation where it makes sense for my ant script to compile two
path properties into one but because ant resolves all location properties to
absolute paths this is problematic. Let's say I have...
<property name="parent.dir" location="parent"/>
<property name="child.dir" location="child"/>
then
${parent.dir}/${child.dir}
will resolve to two absolute paths seperated by a slash. Clealy this wont
work at all.
I cannot use values rather than locations as in then the path seperators are
not converted between / and \ and we have windows and unix build
requirements.
I could define all my paths seperately but this would be a lot of properties
as there are many combinations.
My questions are....
Why does ant have to resolve locations to absolute paths? What is the
advantage of this over working relatively from the basedir?
Is there another way to specify a property as a relative path and still have
the seperators be localized to the platform?
Would anyone be interested if I patched ant to either support...
<property name="path" relativelocation="somepath"/>
or
<property name="path" location="somepath" relative="true"/>?
Thanks for your time
Regards
Wesley Hall
