Ahhh! "addCondition()" is good! Then it *really* is, what I hoped it to be.
Is going to try it.
(Can Peter Reilly also "deprecate" the specific
"add<specific-condition-name>()"-method?? From my point of view, here, it
should be history.)
I have already skipped 1.5.3 - 'Antoine Levy-Lambert' did something cool and
quite useful the other day; I am using Ant-1.6-20030728.
Can not get any simpler.
!
Med venlig hilsen
Morten Sabroe Mortensen
TietoEnator A/S, Ved Lunden 12, 8230 �byh�j, Danmark
mailto:[EMAIL PROTECTED]
http://www.tietoenator.com
-----Original Message-----
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: 30. juli 2003 23:36
To: 'Ant Developers List'
Subject: RE: Implementing "conditions"
In Ant 1.5.x, the Condition framework is not extensible without modifying
Ant's code. In Ant 1.6, just write a class that implements Condition,
<taskdef> it, and use it inside <condition>. Cannot get any simpler, right?
I haven't played with Ant 1.6 at all, so this is all in theory ;-)
If it doesn't work, complain to Peter Reilly who did this (great!) piece of
code ;-) --DD
> -----Original Message-----
> From: Morten Mortensen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 30, 2003 4:28 PM
> To: 'Ant Developers List'
> Subject: RE: Implementing "conditions"
>
> Still, how to implement generic conditions?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
