ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Magesh Umasankar" <>
Subject Re: Ant as a deployment tool
Date Mon, 16 Jun 2003 17:24:12 GMT
In ant-dev, I have proposed a new task to address
situations like yours (it is still experimental):

Using the shar task, you would create a self-extracting
shell that would contain your application, Ant and maybe
even a JRE.  As part of the postscript, you can specify
various environment variables like ANT_HOME, JAVA_HOME,
etc. and invoke ant too.

There are several advantages to this approach (that of
redistributing Ant as part of your install):
1. You don't have to worry if the deployment platform
has the correct Ant version your build file supports.
2. The deployer doesn't have to have Ant installed
as a prerequisite.
3. You can use the power of Ant for installation 
purposes -- tasks like <input>, <copy>, <sql>, etc.

Try the <shar> task (you would have to taskdef it for now) 
and provide feedback on whether that floats your boat.


----- Original Message ----- 
From: "Grinvald, Edward" <>
To: "Ant Users List" <>
Sent: Monday, June 16, 2003 12:58 PM
Subject: Ant as a deployment tool

Hi all,
It seems like ant could be used to deploy an application or a
development environment onto a clean box, either in place of, or
assisting an installation suite. The problem that i'm running into, is
that certain env vars have to be set in order to run ant, like
$ANT_HOME, etc. Has anyone tried running ant on a freshly installed os,
and how would they get around the necessary initial config?



To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message