On Thu, 05 Jul 2001, matt inger <[EMAIL PROTECTED]> wrote: > I understand that your vision of ant does not involve making it a > scripting language. However, like myself, most users need some > basic constructs for flow control. I think the ContainerTask will > definately be a step in that direction allowing users to develop > their own tasks. But, in a lot of cases, the people developing the > ant input files are not necessarily java programmers, and could not > really code up their own tasks, or effectively make their own > conditionals. The idea here is that there will be a "standard" foreach task (and friends) in a repository of optional tasks, it will just not be part of the very core of Ant (just like many current built-in tasks will probably be demoted to optional tasks - <sql>, <cvs> and many others). Stefan
- Re: Target 'build.xml' does not ex... noname23
- Re: Target 'build.xml' does not ex... Rakshit Daga
- RE: for-each (another proposal) Chris Greenlee
- Re: for-each (another proposal) Peter Donald
- Approach to Conditionals: SOMETHIN... matt . inger
- Re: Approach to Conditionals: ... Peter Donald
- Re: Approach to Conditiona... Conor MacNeill
- Re: Approach to Conditiona... matt . inger
- Re: Approach to Conditiona... matt . inger
- Re: Approach to Condi... Peter Donald
- Re: Approach to Condi... Stefan Bodewig
- Re: Approach to C... matt . inger
- RCS (was: Approac... Stefan Bodewig
- Re: for-each (another proposal) Stefan Bodewig
- Re: for-each (another proposal... Peter Donald
- Re: for-each (another prop... Stefan Bodewig
- Re: for-each (another... Larry V. Streepy, Jr.
- Re: for-each (ano... Stefan Bodewig
- RE: for-each (another proposal) Peter Vogel
- RE: for-each (another proposal) Mark Womack
- Re: for-each (another proposal) Scheffler, Mark (MED, GEMS-IT)