The point being that the 'location' variant of <property> is what you're after for parent/child builds that need to pass paths around. The above example is merely that, and may not reflect exactly what you need, but its the idea.
Erik
Karr, David wrote:
When I build my system from the top-level, there are certain libraries relative to the top level that lower-level modules need. I need to pass that information to lower-level builds. At the top level, I have my "basedir", which is set to ".", but in the lower levels, I need to expand that to an absolute path. Is this a reasonable thing to try to do, and if so, how can I do this?-- To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ant-user-help@;jakarta.apache.org>
-- To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ant-user-help@;jakarta.apache.org>
