Re: Some Thoughts on Ant 1.3 and 2.0

[Vincent Bergbauer]

----- Original Message ----- 
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
> What I'd like to see for 1.3
> ============================
> 
> (*) Vincent's submissions in the data type area.
> 
> Collecting command line arguments that occur over and over again for
> example. Vincent, what do you think about <argset> and <arg> as
> separate entities instead of overloading <arg> to be a container and a
> single argument at the same time?
> 
No problem with the names. I am a little busy right now, but I should 
reincorporate my changes within a couple weeks
if the CVS submission rate subsides a bit...


> (*) expanding ${} (almost) everywhere
> 
> This should include all attributes of <project> and <target> - except
> id? - and the #PCDATA sections handled by addText. I'm not sure
> whether the latter would interfere with <script> though.
> 
Let's just leave the <![CDATA[ sections out, and scripts will be happy.
It is simple enough for them to access those value via a project property.


I would like to add a little thing for either 1.3 or 2.0 related to scripting, 
as some issues have been raised related
to the ease of use of scripts.
- Define a simple core API that will be well documented for any script tasks 
within Ant.
  This means that some of the current APIs need to be simplified (a nice little 
list() method in FileSet would be useful).
  My notion of current project would help clean up a lot of APIs, while fancier 
tasks (like Ant) could still straddle 
  projects.
- Allow scripts to define tasks.

Vincent.





_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com