Re: no conditional attribute

2006-08-16 Thread Stefan Bodewig
On Wed, 16 Aug 2006, Martijn Kruithof <[EMAIL PROTECTED]> wrote: > Conor MacNeill schreef: > >>1. Just adding all the logic tasks everyone uses anyway :-) >>2. Adding if/unless processing to Task >>3. Implementing aspect style interface(s) and providing an if/unless >>aspect. [SNIP] > I think I'

Re: no conditional attribute

2006-08-16 Thread Matt Benson
--- Martijn Kruithof <[EMAIL PROTECTED]> wrote: > Conor MacNeill schreef: > > >1. Just adding all the logic tasks everyone uses > anyway :-) > >2. Adding if/unless processing to Task > >3. Implementing aspect style interface(s) and > providing an if/unless aspect. > > > >Thoughts? > > > > > Tre

Re: no conditional attribute

2006-08-16 Thread Martijn Kruithof
Conor MacNeill schreef: 1. Just adding all the logic tasks everyone uses anyway :-) 2. Adding if/unless processing to Task 3. Implementing aspect style interface(s) and providing an if/unless aspect. Thoughts? Treating the options in inverse order. I think that option 3 is most versatile an

Re: no conditional attribute

2006-08-16 Thread Conor MacNeill
Dominique Devienne wrote: > > PS: Note that adding if/unless to gives an implicit > -like. I like it myself, and even proposed to it, but this was > voted down by the commiter that left when @author tags were removed > (don't recall his name. He did the property hook, and was a Tomcat > commiter)

Re: no conditional attribute

2006-08-16 Thread Dominique Devienne
On 8/16/06, Peter Reilly <[EMAIL PROTECTED]> wrote: I think that we should go for 2) adding if/unless to all tasks. It should have the same support as the if/unless in targets. I do not see the need for more complicated condition support (at least at the moment). I would prefer 3. myself (aspec

Re: no conditional attribute

2006-08-16 Thread Peter Reilly
I think that we should go for 2) adding if/unless to all tasks. It should have the same support as the if/unless in targets. I do not see the need for more complicated condition support (at least at the moment). There would be some snags (what about tasks that do not derive from Task, what about

Re: no conditional attribute

2006-08-15 Thread Conor MacNeill
I'm pretty much in agreement with Stefan. If if/unless is going to be in some tasks, it should be in all. It reminds me of a principle from one of my old textbooks: Regularity Principle: Regular rules, without exceptions, are easier to learn, use, describe and implement. Once we go down the if/

Re: no conditional attribute

2006-08-15 Thread Stefan Bodewig
On Tue, 15 Aug 2006, Matt Benson <[EMAIL PROTECTED]> wrote: > I forgot about mutant vs. Myrmidon, was thinking of > Myrmidon when you said mutant. I reread Conor's blog > post on this and you are correct. Looking for any old > code but can't find it yet. http://svn.apache.org/repos/asf/ant/core

Re: no conditional attribute

2006-08-15 Thread Stefan Bodewig
On Tue, 15 Aug 2006, Dominique Devienne <[EMAIL PROTECTED]> wrote: >> I know that this has come up before but I've just finally seen why >> it's so damn useful - > {property.set}/> > > Well, I've been a proponent of this for a long time, For a long time I've taken the more extreme "all tasks or n

Re: no conditional attribute

2006-08-15 Thread Matt Benson
--- Dominique Devienne <[EMAIL PROTECTED]> wrote: > > > I'm still wondering about adding arbitrary > "aspect" > > > attributes to tasks, as Mutant had. > > > > Sounds interesting. I wasn't around while Mutant > was > > under development; how can I learn more? > > I barely was myself. Mutant and

Re: no conditional attribute

2006-08-15 Thread Dominique Devienne
> I'm still wondering about adding arbitrary "aspect" > attributes to tasks, as Mutant had. Sounds interesting. I wasn't around while Mutant was under development; how can I learn more? I barely was myself. Mutant and Myrmydon were two Ant 2.0 competing proposal. They were voted down eventuall

Re: no conditional attribute

2006-08-15 Thread Matt Benson
--- Dominique Devienne <[EMAIL PROTECTED]> wrote: > > I know that this has come up before but I've just > finally seen why > > it's so damn useful - level="verbose" unless=$ > > {property.set}/> > > Well, I've been a proponent of this for a long time, > and I coded up my > own with conditions a

Re: no conditional attribute

2006-08-15 Thread Dominique Devienne
I know that this has come up before but I've just finally seen why it's so damn useful - Well, I've been a proponent of this for a long time, and I coded up my own with conditions a long time ago, which also displayed nicely formatted paths and propertysets. I was using it to display diagnosti

no conditional attribute

2006-08-15 Thread Kev Jackson
Hi, I know that this has come up before but I've just finally seen why it's so damn useful - {property.set}/> I've just run into this now trying to help the BSF guys getting a release candidate out and the build.xml needed a bit of work and this would make so *much* easier. Thoughts? Ke