Huh? What do you mean by aliasing? ${env.CLASSPATH} being the same as
${envAlias.CLASSPATH}? That's not possible AFAIK. If you want to control the
prefix used to access environment properties, then do something like:
<property file="${user.home}/${ant.project.name}.properties" />
<property name="environment" value="env" /> <!-- Default prefix -->
<property environment="${environment}" />
By then you must know the prefix used to access env. vars in the build file,
so how useful is that... Unless you're playing tricks by taking advantage of
that fact somehow!? I must be missing something. --DD
-----Original Message-----
From: White, Joshua A (AG, COMM) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 6:38 AM
To: 'Ant Users List'
Subject: Setting Enviroment alias in properties file
I know that you can alias the system properties by using the following:
<property environment="env">
This allows me to access system variables such as env.CLASSPATH.
I was hoping I could alias this property globally by setting it in a
properties file:
environment="env"
It doesn't seem to work. Is there another way to do this? (Besides passing
it in as a command line arg.)
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all
copies.
--
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]>
