Good call on the sub shells. Thanks for the help!
-Original Message-
From: Chuck Holzwarth [mailto:[EMAIL PROTECTED]
Sent: Monday, January 07, 2008 8:17 AM
To: Ant Users List
Subject: RE: environment attribute
Try using the ant exec task to run the env command. Are you sure the
, 2008 3:03 PM
To: Ant Users List
Subject: Re: environment attribute
I just tried this on a Solaris VM on my desktop and HOSTNAME is not
defined by default. You may want to issue "export HOSTNAME=`hostname`"
in your .profile. Change this as appropriate for your shell.
Dominique Devienne
25100-10
[EMAIL PROTECTED]
~/cruisecontrol/projects/webnew-dec2007/netsoft/webnew
$ echo $OSTYPE
solaris2.10
Thanks,
Barry
-Original Message-
From: Chuck Holzwarth [mailto:[EMAIL PROTECTED]
Sent: Friday, January 04, 2008 3:03 PM
To: Ant Users List
Subject: Re: environment attribute
I
I just tried this on a Solaris VM on my desktop and HOSTNAME is not defined by
default. You may want to issue "export HOSTNAME=`hostname`" in your .profile.
Change this as appropriate for your shell.
Dominique Devienne <[EMAIL PROTECTED]> wrote: On 1/4/08, Barry Pape wrote:
> Hopefully this is
On 1/4/08, Barry Pape <[EMAIL PROTECTED]> wrote:
> Hopefully this is a quick and easy question. Is the environment
> attribute of the property task supported on Solaris?
Yes.
> I've been trying
> to use ${env.HOSTNAME} but it doesn't appear to resolve.
Most likely because you have no such env.
