I'm not -1 because whether they are there or not is not relevant to my
needs. I don't use them in my own builds. I don't need them.
Open-source is all about everyone doing the things they want to do
development-wise.... "scratching an itch" is the term thrown around on the
Jakarta lists quite often.
As for the others, the issue just got raised today on ant-user.... while
most committers are here also, its probably best to discuss this kind of
thing on ant-dev.
When workarounds exist and they are quite painless (such as getting a new
JAR and adding a <taskdef>) then there is little incentive to change things.
I'm not dodging any issue - its simply not realistic for the Ant 1.5 cutoff,
which is literally right NOW! Bring it up on ant-dev when the dust settles
from the Ant 1.5beta release and see where you get. A +0 is not going to
keep it from happening, so if you convince others to vote for it then you
might just get what you want.
Erik
----- Original Message -----
From: "Dominique Devienne" <[EMAIL PROTECTED]>
To: "'Ant Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, April 30, 2002 2:21 PM
Subject: RE: "if" task
> Dodging the issue I see. How sad. Especially when one sees what's get
> "dumped" to 1.5 all the time by following ANT-dev. You're not really +0 it
> seems to me, just finding excuses for not appearing -1. And the silence of
> other -1's is also so telling I'm afraid. So much for the community
> aspect... That product-specific optional tasks get pushed back to the
> product they support is fair, but in this case it's just not right. --DD
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
