I had the same prob for a bit with ANT and iPlanet iAS.
What I found is that I was using mkstool kit and its ksh shell to do my ant
builds (that is I would issue 'ANT' from a ksh prompt). MKS toolkits KSH
needed "iasdeploy.bat" as the executable name (in the ant build.xml) rather
that just plain old "iasdeploy". Running the same ANT build.xml under a
vanilla cmdprompt (WinNT 4ws sp6) seemed to work fine (with either
'iasdeploy' or 'iasdeploy.bat'. Other non CMD shells (eg. cygwin) might
have the same problem.
Ultimately, I made a property (eg. dplcmd) and used that as the executable
in the exec task. We use props files here to allow for local workstation
variations, and the main build.xml has the default value of 'iasdeploy' for
this property. Developers can then override the property in their private
props file to call 'iasdeploy.bat' if needed.
Hope this helps,
-Fred
-----Original Message-----
From: jaideep satghare
To: [EMAIL PROTECTED]
Sent: 4/25/01 2:38 AM
Subject: Re: Problem with iasdeploy using ANT 1.2
The path does contain the deployment tool and the same
command works when executed from the cmd shell, that
is the deployment goes thru.
Jaideep
--- Peter Donald <[EMAIL PROTECTED]> wrote: > Could
you check that your path contains the
> deploying tool and that the
> same command line will run from cmd shell.
>
> Cheers,
>
> Pete
>
>
*-----------------------------------------------------*
> | "Faced with the choice between changing one's
> mind, |
> | and proving that there is no need to do so -
> almost |
> | everyone gets busy on the proof."
> |
> | - John Kenneth Galbraith
> |
>
*-----------------------------------------------------*
>
____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com
