ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <co...@cortexebusiness.com.au>
Subject Re: Pausing Ant
Date Sat, 18 Aug 2001 00:06:45 GMT
Matthew,

A couple of points. In Ant 1.4 we will have the ability to run multiple
tasks at a time so we need to coordinate access to the user for input.
Also, when Ant is embedded in a GUI, there is no way it should be reading
from System.in - it needs a way (interface) to interact with the GUI or
whatever system in which it is embedded.

My idea is to define an interface, say InputProvider. The project object
will be given an instance which implements this interface. You should ask
this instance for input. If you do, then, when someone runs Ant from a GUI,
the GUI can provide a suitable class that provides an InputProvider, say
DialogBoxInputProvider. For the standard Main command-line launcher, a
CommandLine input provider which reads from System.in would be used. Other
possibilities would be an InputProvider for unattended operation which can
return default responses etc.

It needs more thought, especially when running Java tasks which expect
input, informing the user which task they are actually talking to, etc,
etc. That should, however, give you some ideas about the issues.

Conor

----- Original Message -----
From: "J. Matthew Pryor" <matthew_pryor@versata.com>
To: <ant-user@jakarta.apache.org>
Sent: Saturday, August 18, 2001 4:31 AM
Subject: RE: Pausing Ant


> Conor,
>
> Can you explain your comment a little more ?
>
> Thanks,
> Matthew
>
> > -----Original Message-----
> > From: Conor MacNeill [mailto:conor@cortexebusiness.com.au]
> > Sent: Friday, August 17, 2001 3:26 AM
> > To: ant-user@jakarta.apache.org
> > Subject: Re: Pausing Ant
> >
> >
> > Just a warning. Task input, prompting, etc will most likely change
> > significantly after the 1.4 release.
> >
> > Conor
> >



Mime
View raw message