Sorry, should have explained better.
Given build.properties at root level with the following property
natives.dir=${user.dir}/natives
Also, a build.xml at root level that includes it with <property
file="build.properties>, and a build.xml in a "natives" that includes it
with <property file="../build.properties">
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.
Thnaks.
John
-----Original Message-----
From: Diane Holt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19, 2002 1:01 PM
To: Ant Users List
Subject: RE: Ant design question(s) - #1
--- "Guthrie, John" <[EMAIL PROTECTED]> wrote:
> There* is* a problem with using a build.properties 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?
Diane
=====
([EMAIL PROTECTED])
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/
--
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]>
