Return-Path: 
 <user-return-60431-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 94837 invoked from network); 19 Apr 2007 06:10:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 19 Apr 2007 06:10:33 -0000
Received: (qmail 29711 invoked by uid 500); 19 Apr 2007 06:10:38 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 28678 invoked by uid 500); 19 Apr 2007 06:10:36 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 28667 invoked by uid 99); 19 Apr 2007 06:10:36 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 23:10:36 -0700
X-ASF-Spam-Status: No, hits=0.6 required=10.0
	tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [193.109.238.66] (HELO dnsinet.rzf-nrw.de) (193.109.238.66)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 23:10:28 -0700
Received: from z011100.bk.fin.local (z011100.bk.fin.local [172.18.101.140])
	by dnsinet.rzf-nrw.de (8.14.0/8.14.0) with ESMTP id l3J6A50q020983
	for <user@ant.apache.org>; Thu, 19 Apr 2007 08:10:06 +0200
Received: from z011034.bk.fin.local ([130.11.7.34]) by z011100.bk.fin.local
 with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 19 Apr 2007 08:10:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: ant property not set question
Date: Thu, 19 Apr 2007 08:10:05 +0200
Message-ID: <EF39D77A486C234B9D9933091CE6D21E24F2B1@z011034.bk.fin.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ant property not set question
Thread-Index: Acd+B0EQHXPQiD+FQcOdNlzEQFterwD0g6gQABvPt5A=
From: <Jan.Materne@rzf.fin-nrw.de>
To: <user@ant.apache.org>
X-OriginalArrivalTime: 19 Apr 2007 06:10:05.0901 (UTC)
 FILETIME=[600C97D0:01C78249]
X-Virus-Checked: Checked by ClamAV on apache.org

I think Rob means, that you could delete all your is.dev.home occurences =
and
just using env.IS_DEV_HOME.
If you want to define that in a propery file just use
  env.IS_DEV_HOME=3DsomeValue
It's "just" a normal property ...

But personally I prefer using different properties. So you are free to =
do more
complicated stuff without modifying the rest of your buildfile


	<!-- Check env variables with different writings -->
	<condition property=3D"is.dev.home" value=3D"${env.IS_DEV_HOME}"><isset =
property=3D"env.IS_DEV_HOME"/>...	<condition property=3D"is.dev.home" =
value=3D"${env.is_dev_home}"><isset property=3D"env.is_dev_home"/>...
	<!-- checks standard installation paths -->
	<available property=3D"is.dev.home" ... >
	<condition ... >


Jan


>-----Urspr=FCngliche Nachricht-----
>Von: Anderson, Rob (Global Trade) [mailto:Rob.Anderson@nike.com]=20
>Gesendet: Mittwoch, 18. April 2007 18:51
>An: Ant Users List
>Betreff: RE: ant property not set question
>
>Forget about is.dev.home, you don't need it. Just use the environment
>variable only...
>
><fail unless=3D"env.IS_DEV_HOME"=20
>message=3D"IS_DEV_HOME/is.dev.home variable
>is not set."/>
>
>-Rob Anderson
>=20
>
>> -----Original Message-----
>> From: Philip Swenson [mailto:pswenson@webmethods.com]=20
>> Sent: Friday, April 13, 2007 1:06 PM
>> To: user@ant.apache.org
>> Subject: ant property not set question
>>=20
>> I have a property that is declared like this:
>>=20
>> =20
>>=20
>>     <property name=3D"is.dev.home" value=3D"${env.IS_DEV_HOME}"/>
>>=20
>> =20
>>=20
>> So if an environment variable is set then the value gets set.=20
>>  However if a build.properties file exists, this value can be=20
>> overridden in the properties file like :  is.dev.home=3Dc:/blah
>>=20
>> =20
>>=20
>> This works fine.... Howeverk, I want to validate that the=20
>> property has been set in one of the two methods (env variable=20
>> or properties file) by doing
>> this:
>>=20
>> =20
>>=20
>>         <fail unless=3D"is.dev.home"=20
>> message=3D"IS_DEV_HOME/is.dev.home variable is not set."/>
>>=20
>> =20
>>=20
>> This doesn't work, because the value of is.dev.home becomes=20
>> "$is.dev.home"
>> literally if the value isn't set.  I know this because=20
>> further down the path I get this message instead of my=20
>> failure message:
>>=20
>> [copy] Copying 27 files to C:\dev\hoth\dev\${env.IS_DEV_HOME}
>>=20
>> =20
>>=20
>> Any ideas on how to make this validation work?
>>=20
>> =20
>>=20
>> Thanks
>>=20
>> phil
>>=20
>> =20
>>=20
>> =20
>>=20
>>=20
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>For additional commands, e-mail: user-help@ant.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org