ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Kirkpatrick <>
Subject Re: AW: http request handling
Date Fri, 26 Mar 2010 08:47:39 GMT
I initially submitted my use case to the antForm guys - see the spec and 
discussion in attachment.

An ant-embedded http server looks to me as a natural extension to the 
ant-contrib AntServer task.

Of course the purpose is not to play the role of a classical Web server, 
but well to drive a build process via a http monitoring client.
So the http inbound requests should IMO be handled by some ant target 
with form input values assigned to ant properties.
 >From the build process side, this is very similar to command-line 
properties, but from the user/client point of view, it is very different.

In this use case, the server would startup and shutdown together with 
the build process, replying to the monitoring console requests working 
as an exclusive client. So it should not wait for incoming requests 
during execution of  the top-level targets.
One could conceive a wider scope: serving multiple simultaneous clients 
for independent builds, then a separate http listener would be required! 
but this is far off my needs.

I don't know Hudson, I will check.

Robert. a écrit :
> Ant is a buildtool.
> Letting the build waiting for incoming HTTP requests will slow down the build and I dont
see any reason why.
> So could you please elaborate about your use case?
> - who will create the http request
> - what kind of request is it
> - what data in the requests
> - what should the 'handler' (Ant/something else?) do with that
> Maybe Ant is not the right tool for that ... 
> E.g. if a request should start a build, the use of a CI server like Hudson is the better
> Jan
>> -----Ursprüngliche Nachricht-----
>> Von: Robert Kirkpatrick [] 
>> Gesendet: Mittwoch, 24. März 2010 19:17
>> An: Ant Users List
>> Betreff: Re: http request handling
>> I imagined that the ant plugin fulfilled the Jetty slogan 
>> "Don't deploy 
>> your application in Jetty, deploy Jetty in your application".
>> I still believe this has a potential.
>> Regards,
>> Robert.

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

View raw message