ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Feller" <Emmanuel.Fel...@free.fr>
Subject Re: failonerror; general solution
Date Thu, 09 Oct 2003 11:26:10 GMT
Hello,

I not agree on all ...

The <if/> is not a good thing, and especially in big builds.
My builds are quite comlex and I reduce complexity by
developping my own tasks : this is the official way and
(IMHO) should be promoted. I developped wrapper around
conditionnal things but now I have access to macro by
<macrodef/>, and I think i will refactor my build around
this. So i think than the <if/> has no place in ANT any
more, if it could had one. The same things for <foreach/>.

I think than Ant 1.6 is a quite revolution (cleaner ways,
simpler ways), so i do not want it to be misunderstood.(In
My Humble Opinion)

I use the try/catch, and it could be shipped but I do not
want that it convince newbies than Ant is a scripting
framework. It is a real danger.

For the propertyCopy, i use it a lot, but i am searching a
cleaner way to do it. On this i do not have an opinion.

Emmanuel
----- Message d'origine ----- 
De : "Jose Alberto Fernandez" <jalberto@cellectivity.com>
À : "Ant Developers List" <dev@ant.apache.org>
Envoyé : jeudi 9 octobre 2003 12:59
Objet : RE: failonerror; general solution


To tell you the truth I think that the 5(?) tasks of
antcontrib are just a necesity if you try to write
large ANT scripts that must be maintainable by more than one
person.

The <if/> task helps reduce the amount of temporary
variables ant
special init-targets and intermediate targets whose only
need is to
check for a property being set or not.

<trycatch/> speaks for itself.

In my builds, at least, <foreach/> is a necesity, since many
of my
modules
must be build several times with different configuration
parameters.
And the number of configurations is configurable.

The other ones, <propertycopy> and others are just good.

This is why I think we should ask for permission to ship it
as an
antlib.
It will serve as an example of the power of the framework.

> -----Original Message-----
> From: Gus Heck [mailto:gus-antdev@cognition.olin.edu]
> Sent: 08 October 2003 19:58
> To: Ant Developers List
> Subject: Re: failonerror; general solution
>
>
>
> >I'm not as eager to see the tasks in Ant proper as
others,
> that's why I
> >haven't taken any initiative here (in Apache speak,
that's the
> >difference between my +0 and the +1s that have been cast
by others).
> >
> >
> >
> Are we talking about all ant-contrib tasks or just
try/catch?
> I thought
> just try/catch...
>
> -Gus
>
>
> ----------------------------------------------------------
-----------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message