ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guthrie, John" <>
Subject RE: Ant design question(s) - #1
Date Tue, 19 Mar 2002 18:32:23 GMT
Sorry, should have explained better.

Given at root level with the following property
Also, a build.xml at root level that includes it with <property
file=">, and a build.xml in a "natives" that includes it
with <property file="../">

When I run ant at root level, the property gets evaluated (correctly)
because user.dir = root directory. If I cd into natives subdir, user.dir is
now root/natives so the natives.dir evaluates incorrectly.

Yes? What I am looking for here is a way to have my properties defined in a
single place and yet be able to run ant from any of the directories.


-----Original Message-----
From: Diane Holt []
Sent: Tuesday, March 19, 2002 1:01 PM
To: Ant Users List
Subject: RE: Ant design question(s) - #1

--- "Guthrie, John" <> wrote:
> There* is* a problem with using a at the root level and
> having all of the build.xml's reference it. The problem is that some of
> the properties piggyback off of ${user.dir} which is different when
> running ant in different subdirs. E.g. I have a property:
>   natives.dir=${user.dir}/natives
> where my native source code is. Works for the root-level build.xml, but
> not the one in the natives subdir.

In what way doesn't it work?



Do You Yahoo!?
Yahoo! Sports - live college hoops coverage

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message