----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 21, 2001 7:37 AM
> > Am I at least in the same ballpark as the ideas being discussed here?
>
> Sorta .. well actually no. We are talking how the container would support
> such tasks. While you are talking about the infrastructure the task must
> create to make script writing easy ;)
But if the container supports the capability (which it already does for Java
written Tasks) to allow script tasks to be introspected (in some way,
perhaps via some metadata provided from the script task itself) and have
rich types (i.e. filesets) handed to them for free, then that directly
impacts the infrastructure and complexity required for developing a script
task. Or am I still barking up the wrong tree?
I'm certainly not an advocate for using <script> in a build generally
speaking (contrary to popular belief! :), but the <script> issue we're
discussing seems to me to be implicitly related to issues that have been
discussed such as the "container" concept.
Erik
