RE: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Matt Benson
--- Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote: [SNIP] But are there enough usages > as to grant the > definition of a full framework for this pattern. That's backwards... the original idea was not a full framework to support this pattern... this pattern is only one possible way to exploit

RE: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Jose Alberto Fernandez
Your example has this assumption, quite thin for the general case that no matter what accion, the set of other attributes and elements must be exactly the same. I really do not see to much of the usability gain in something like that. Usually you expect different input for different actions. And w

RE: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Matt Benson
--- Dominique Devienne <[EMAIL PROTECTED]> wrote: > This actually ties back to what Magesh proposed (the > dispatch task). > > One of the useful bit his proposal allowed was to > conditionally > execute one mode or the other thanks to > mode="${mode}", where > mode can be configured/computed befor

RE: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Dominique Devienne
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > On Fri, 4 Jun 2004, Matt Benson <[EMAIL PROTECTED]> wrote: > > If there is any reason why we couldn't/shouldn't have > > a generic DynamicConfigurator that could > > execute an arbitrary task by classname, and a generic > > or , probably also a >

Re: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Stefan Bodewig
On Fri, 4 Jun 2004, Matt Benson <[EMAIL PROTECTED]> wrote: > If there is any reason why we couldn't/shouldn't have > a generic DynamicConfigurator that could > execute an arbitrary task by classname, and a generic > or , probably also a > DynamicConfigurator, to instantiate (and optionally > con

Re: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Matt Benson
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Thu, 3 Jun 2004, Matt Benson > > Sorry, what is your question? > If there is any reason why we couldn't/shouldn't have a generic DynamicConfigurator that could execute an arbitrary task by classname, and a generic or , probably also a DynamicC

Re: Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-04 Thread Stefan Bodewig
On Thu, 3 Jun 2004, Matt Benson <[EMAIL PROTECTED]> wrote: > --- Matt Benson <[EMAIL PROTECTED]> wrote: >> > /> >> > > The above reminds me of something... for one thing, > that should have been a in that context, but > anyway... > > what would be the ramifications of having > > > ... > > >

Generic tasks/types WAS Possible Ant 1.7 alpha bug: property expansion.

2004-06-03 Thread Matt Benson
--- Matt Benson <[EMAIL PROTECTED]> wrote: > /> > The above reminds me of something... for one thing, that should have been a in that context, but anyway... what would be the ramifications of having ... and Et cetera? -Matt __