ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wolfgang haefelinger <whaefelin...@gmail.com>
Subject Re: AW: http request handling
Date Sun, 28 Mar 2010 17:21:44 GMT
Robert,

so I assume you are looking for some kind of "graphical" user
interface to let you users make proper choices about "build options"
(i.e. property values).

Anyway, something like this does not exist in Ant - and probably never
will. CI tools would be an overkill -- agreed -- but worse, property
handling is not supported to my knowledge.

I'm afraid to say that you have to start hacking yourself ;-)


On Sun, Mar 28, 2010 at 6:26 PM, Robert Kirkpatrick <robert@eridan.net> wrote:
> Wolfgang,
>
> Thank you for your attention.
> Please find the use case in attachment - I get a spam error when attached to
> a mail to the ant user list.
>
> Basically you have got it: I have a build which runs like your 3.b and I
> would like to call it like your 3.a.
>
> Currently I use a work-around (in Windows) via an ActiveX shell script, but
> this solution is awful.
>
> I believe that CI servers do similar jobs very well, but to me it is an
> overkill.
>
> Robert.
>
> wolfgang haefelinger a écrit :
>>
>> Robert,
>>
>> to get a decent response, it would be wise to elaborate in your own
>> words what you would like to (a) achieve and (b) how this could be
>> done with ant.
>>
>> To me, it looks like this:
>>
>> 1. You have a project that you can build with Ant; so there is a
>> build.xml with some targets (clean, compile, test, package, ..)
>> 2. Then someone would startup ant in "server mode" for this particular
>> project: A "http" server gets started and lists on a particular port
>> (say 5000) for incoming requests.
>> 3. Now the project can be compiled by saying something like
>>
>>    $ curl http://localhost:5000/compile?p1=v1&p2=v2
>>
>>  which would be essentially the same as doing a "batch" compilation like
>>
>>     $ ant -Dp1=v1 -Dp2=v2 compile
>>
>> 4. Eventually you would shutdown the server via
>>
>>     $ curl http://localhost:5000/shutdown
>>
>>
>> However, perhaps you have something totally different in mind?
>>
>> Btw, CruiseControl, Hudson, Anthill, Teamcity and all other continuous
>> integration servers are well suited for triggering builds via http
>> requests...
>>
>> // Wolfgang.
>>
>>
>> On Sun, Mar 28, 2010 at 2:30 PM, Robert Kirkpatrick <robert@eridan.net>
>> wrote:
>>
>>>
>>> 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.
>>>
>>> Jan.Materne@rzf.fin-nrw.de 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 choice.
>>>>
>>>>
>>>> Jan
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> -----Ursprüngliche Nachricht-----
>>>>> Von: Robert Kirkpatrick [mailto:robert.kirkpatrick@skynet.be] 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: user-unsubscribe@ant.apache.org
>>> For additional commands, e-mail: user-help@ant.apache.org
>>>
>>>
>>>
>>
>>
>>
>>
>



-- 
Wolfgang Häfelinger
häfelinger IT - Applied Software Architecture
http://www.haefelinger.it
+31 648 27 61 59

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message