Thank you Wolfgang for your useful insights.
Your definition of a configuration is indeed the result of the user
request: an http form submission translated into a set of ant properties.
The dedicated web client makes sure a consistent set is produced.
In my use case, the build is directly tri
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, pro
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, t
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
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 bu
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 bu
> you can use to block for data; getting the values
> in depends
> on the format. Me, I have servlets that push out .properties files
>
>
> http://localhost/myapp/index.html"/>
>
Ok, so you are not reading the http request 'directly' ...
- start the http server:
- wait for him unti
On 25/03/2010 05:27, jan.mate...@rzf.fin-nrw.de wrote:
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
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 'handle
My expectation in the ant-jetty plugin is to turn ant into a http server
so that incoming requests could be handled in ant.
Robert.
jan.mate...@rzf.fin-nrw.de a écrit :
What is "http handling"?
Do you want that Ant does the OUTGOING request or handles the INCOMING request?
outgoing:
- core
What is "http handling"?
Do you want that Ant does the OUTGOING request or handles the INCOMING request?
outgoing:
- core task
http://ant.apache.org/manual/CoreTasks/get.html
- http antlib
http://svn.apache.org/repos/asf/ant/sandbox/antlibs/http/
http://svn.apache.org/repos/asf/ant/sandb
11 matches
Mail list logo
