Even though "It makes build files clearer, easier to understand, and remove the need for having so many (private) targets with dependencies between them as a direct consequence of the current only built-in scheme to do conditional execution.", do these benefits not amount to a convenience? Like electric lights... I could wait until morning and go outside to be able to see things, or I could turn on the light if only it is provided to me. The light is much more convenient, but other ways exist to see things! Similarly, <if> does not provide anything from a functional perspective that cannot be accomplished some other way in Ant (I don't think).
-Matt --- Dominique Devienne <[EMAIL PROTECTED]> wrote: > I disagree. It's not only a convenience! It makes > build files clearer, > easier to understand, and remove the need for having > so many (private) > targets with dependencies between them as a direct > consequence of the > current only built-in scheme to do conditional > execution. Conditions in real > project building happen all the time, and the > current mechanism supports it > in a very ugly fashion. Many people use Ant proper > only, and thus not > providing <if> built-in is in effect stopping it's > use. > > Conor's proposal allowing to do: > > <target name="x"> > <do-something/> > <depend target="x" > if="do-something-set-property"/> > </target> > > would are removed much of the need for <if> and > avoided the current > multiplication effect on target number, but we ain't > gonna have that ever > from the looks of it!!! > > So NO, <if> is not just a convenience! --DD > > -----Original Message----- > From: Matt Benson [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 22, 2002 9:20 AM > To: Ant Users List > Subject: Re: conditional copy > > I completely agree that the functionality is the > same; > the <if> task only adds a minor convenience. > > -Matt > > --- Erik Hatcher <[EMAIL PROTECTED]> > wrote: > > Its only fair to also add that the <if> task > doesn't > > really add anything > > to what can be done with conditional targets - an > if > > and an unless > > target could be used to handle both if/else types > of > > conditions. > > > > So you aren't really using a "conditional task", > > you're using a task > > container that switches which sets of tasks it > > executes based on some > > property. > > > > 6 of one.... > > > > Erik > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
