ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-ant/proposal/sandbox/input README
Date Mon, 22 Apr 2002 12:08:13 GMT
bodewig     02/04/22 05:08:13

  Modified:    proposal/sandbox/input README
  We have moved.
  Revision  Changes    Path
  1.5       +6 -60     jakarta-ant/proposal/sandbox/input/README
  Index: README
  RCS file: /home/cvs/jakarta-ant/proposal/sandbox/input/README,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- README	18 Apr 2002 12:34:42 -0000	1.4
  +++ README	22 Apr 2002 12:08:13 -0000	1.5
  @@ -1,62 +1,8 @@
  -Ant's current CVS version contains an <input> task that gathers user
  -input by reading from - this is not too nice for people
  -embedding Ant in IDEs. 8-)
  +The input proposal has been accepted as part of main Ant and has been
  +merged with the main code tree on 2002-04-22.
  -<input> also supports an undocumented testinput attribute that is used
  -by Ant's test cases to allow them to run without user interaction, but
  -could also be used to provide predefined answers to unattended builds.
  +The only part that didn't get moved over was SwingInputHandler that
  +has never been more than a proof of concept - if you really want to
  +see it, you can find it in CVS's Attic:
  -This proposal tries to define a very basic input framework for Ant
  -that would allow Ant to be easily embedded into IDEs via
  -implementations of the
  -interface.  At the same time an implementation of the interface is
  -provided that allows the input to be specified via an external
  -property file.
  -There are three implementations of the InputHandler interface,
  -DefaultInputHandler which reads form just like the <input>
  -task originally did, PropertyFileInputHandler for non-interactive
  -builds and SwingInputHandler which is nothing more than a proof of
  -Input requests get encapsulated in instances of the class - or subclasses thereof
  -- which provide a method to also validate the input, moving this
  -responsibility from the <input> task to the InputRequest itself.
  -There are two types of InputRequests ATM, InputRequest encapsulates a
  -request for a simple unrestricted text input,
  -MultipleChoiceInputRequest is a request where valid inputs are
  -restricted to a given set of values.
  -If you run ant on the build file in this directory, a version of
  -ant.jar will be created in the build subdirectory that is identical to
  -the main trunk of Ant except for the input task itself and two minor
  -changes to Project and Main, that allow InputHandlers to be plugged in
  -programmatically or via a commandline switch -inputhandler.
  -With this version of Ant, run the input.xml build file in
  -proposals/testcases, Ant should behave the same way the input task for
  -the main branch does - except that it won't allow you to enter invalid
  -input in the multi target.
  -If you invoke Ant like this:
  -ant -f proposal/sandbox/input/src/testcases/input.xml -inputhandler
  -You'll get the ugliest dialog you've ever seen, but it works ;-)
  - ant -f proposal/sandbox/input/src/testcases/input.xml -inputhandler
  -to see the non-interactive build process in action.
  -provides a sample of possible input failures.
  -The original testcase for <input> has been ported to the new framework
  -as well, run it via
  -ant run-test
  -in this directory.
  \ No newline at end of file

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

View raw message