Re: property environment="env" doesn't work everywhere

PROTECTED] Sent: Wednesday, May 04, 2005 2:09 PM To: Ant Users List Subject: Re: property environment="env" doesn't work everywhere True, just bugs me why it works in one place but not another. On May 4, 2005, at 5:03 PM, Alexey N. Solofnenko wrote: ANT_HOME environment variable jus

RE: property environment="env" doesn't work everywhere

>> To: Ant Users List >> Subject: Re: property environment="env" doesn't work everywhere >> >> >> True, just bugs me why it works in one place but not another. >> >> >> On May 4, 2005, at 5:03 PM, Alexey N. Solofnenko wrote: >>

RE: property environment="env" doesn't work everywhere

Is there a difference in the way you are running ant on each box? Perhaps via cron? -Rob Anderson > -Original Message- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 04, 2005 2:09 PM > To: Ant Users List > Subject: Re: property environment=&qu

Re: property environment="env" doesn't work everywhere

Hi, 04May2005 @ 17:09 EJ Ciramella thusly spake > True, just bugs me why it works in one place but not another. No 2 boxes are exactly the same. Even you ghost 2 boxes you'll still have differences due to hardware. Setting up the 2 boxes there would've differences in the order you installed softw

Re: property environment="env" doesn't work everywhere

True, just bugs me why it works in one place but not another. On May 4, 2005, at 5:03 PM, Alexey N. Solofnenko wrote: ANT_HOME environment variable just sets ant.home system property that ANT uses internally. Usually ANT can guess its home directory, so setting the environment variable is not a

Re: property environment="env" doesn't work everywhere

[mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 1:54 PM To: Ant Users List Subject: Re: property environment="env" doesn't work everywhere That's what I did, so instead of doing and later using things like ${env.ANT_HOME}, I just use ${ant.home}, why did this change and

RE: property environment="env" doesn't work everywhere

e- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 1:54 PM To: Ant Users List Subject: Re: property environment="env" doesn't work everywhere That's what I did, so instead of doing and later using things like ${env.ANT_HOME}, I just use ${ant.home},

Re: property environment="env" doesn't work everywhere

ANT_HOME environment variable just sets ant.home system property that ANT uses internally. Usually ANT can guess its home directory, so setting the environment variable is not always necessary. - Alexey. EJ Ciramella wrote: That's what I did, so instead of doing and later using things like ${en

Re: property environment="env" doesn't work everywhere

That's what I did, so instead of doing and later using things like ${env.ANT_HOME}, I just use ${ant.home}, why did this change and why does this work in some places and not in others? Both work on my mac, but this is weird. On May 4, 2005, at 4:50 PM, Dominique Devienne wrote: From: EJ Cirame

RE: property environment="env" doesn't work everywhere

> From: EJ Ciramella [mailto:[EMAIL PROTECTED] > > Has anyone else seen this behavior? I used env.ANT_HOME on one box and > it didn't get expanded, but on another, it worked just fine. Both > machines are running: > > [EMAIL PROTECTED]:~# uname -a > Linux testbuild 2.6.11.7 #1 Tue Apr 12 17:04:

property environment="env" doesn't work everywhere

Has anyone else seen this behavior? I used env.ANT_HOME on one box and it didn't get expanded, but on another, it worked just fine. Both machines are running: [EMAIL PROTECTED]:~# uname -a Linux testbuild 2.6.11.7 #1 Tue Apr 12 17:04:43 EDT 2005 i686 unknown unknown GNU/Linux and ant 1.6.1 ?