will hopefully be released shortly, there is a vote running for it
atm on the ant-dev list.
Maarten
- Original Message
From: "Kanjo, Samer" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 8:00:22 PM
Subject: RE: Dependency Resolution Problems i
call the targets in the
other build file. Use the input task the prompt for the environment.
-Rob A
> -Original Message-
> From: Kanjo, Samer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 01, 2006 11:54 AM
> To: 'Ant Users List'
> Subject: RE: Targeting Multipl
006 11:28 AM
To: Ant Users List
Subject: RE: Targeting Multiple Environments
Comments below...
> -Original Message-----
> From: Kanjo, Samer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 01, 2006 7:29 AM
> To: 'Ant Users List'
> Subject: RE: Targeting Multiple Envir
user-friendly error message or input task if
the TARGET_ENV prop is missing:
You must specify TARGET_ENV on the command
line. For example...
ant -DTARGET_ENV=dev deploy
Or:
...
Why are you not satisfied with this solution?
-Rob A
> -Original Message-
> From: Kanjo, Samer [mailto:[EMAI
I am curious as to how others are using Ant to target multiple environments
such as development, test, training, and production. In my world each
environment typically has its own set of databases, servers, and application
servers.
What I have done is externalize all properties into a set of prope
