Not sure if this is what you want to do, but you could invoke ANT programmatically from a java application and handle the user interaction however you want. The only trick is to catch the exit from ANT in your app. If this sounds like it would help, let me know and I'll give you more details.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 12:31 PM
To: [EMAIL PROTECTED]
Subject: Re: preventing ant exit
shoot i'm running 1.2 ghz/512mb here.... strange that it does load so slow.
maybe a disk issue.
anyhow, if user presses enter then run repeat all targets. no pause between
targets, wouldn't want that.
out of, well, impatience, i decided to try coding this in. it's a fairly
simple hack, works really well. doesn't seem to leak memory over time or
anything.
thanks
troy
"T Master"
<tmaster@iknowled To: <[EMAIL PROTECTED]>
geinc.com> cc:
Subject: Re: preventing ant exit
07/18/2001 02:18
PM
Please respond to
ant-user
That is similar to asking javac for keyboad input to quit after compiling.
Workarounds: kill unnecessary processes on your box to allow more cpu time
to ant; upgrade your box :-)
If the user did press <ente> which target would be run then? The previous
or the next in line?
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 18, 2001 12:58 PM
Subject: preventing ant exit
>
> hi
>
> i'm new to ant...
>
> was just wondering if there was any reason nobody has added an option to
> run ant in a loop. that is, the only way it seems to run is
>
> $ant compile
> <barf>
> $ant compile
> <barf>
> $ant compile
> BUILD SUCCESSFUL
> $
>
> which is sort of slow on my pc because each time ant has to load
> (impatience *is* one of the three pillars of programming.)
>
> better would be:
>
> $ant compile
> <barf>
> q to quit, enter to continue:
> <barf>
> q to quit, enter to continue:
> BUILD SUCCESSFUL
> q to quit, enter to continue:Q
> $
>
> ?
>
> thanks
> troy
>
