Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=c04/0UcT2liDFFKlTNahOnUo2HofQUb+FtypEyMLWdSDLNGBWKQ+0YsIWpjnAtdAZQbpEsKSIAluPBtxFnj804LgMYy9I3hid+C6w2o5rDlbNsD1iV+5MPVcYyYk+i/dLI696JxZteD7DkJuwwaTbj9EaGPeFIf/PoZiRQf458U=;
Message-ID: <296414.15814.qm@web51307.mail.re2.yahoo.com>
Date: Thu, 19 Aug 2010 09:59:25 -0700 (PDT)
From: Vimil Saju <vimilsaju@yahoo.com>
Subject: Re: AW: Conditional target problem
To: Ant Users List <user@ant.apache.org>
In-Reply-To: <06080D44730F41428BAF2168FA8BDD8004C8DBB4@icsrv02.icongmbh.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1816305784-1282237165=:15814"

--0-1816305784-1282237165=:15814
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

I read about the new macrodef task which can be used create a custom compos=
ite task by combining other tasks together. Using the macrodef task instead=
 of antcall cant we overcome the performance overhead and the property visi=
bility issues with antcall?

--- On Thu, 8/19/10, Knuplesch, Juergen <Juergen.Knuplesch@icongmbh.de> wro=
te:

From: Knuplesch, Juergen <Juergen.Knuplesch@icongmbh.de>
Subject: AW: Conditional target problem
To: "Ant Users List" <user@ant.apache.org>
Date: Thursday, August 19, 2010, 8:03 AM

Antcallback gives back some props you define

-----Urspr=FCngliche Nachricht-----
Von: Niklas Matthies [mailto:ml_ant-user@nmhq.net]=20
Gesendet: Mittwoch, 18. August 2010 15:55
An: Ant Users List
Betreff: Re: Conditional target problem

On Tue 2010-08-17 at 16:20h, Vimil Saju wrote on user:
> I know ant is supposed to be declarative language as opposed to a
> procedural one, but whats wrong with using the 'if' task provided
> with ant-contrib along with "ant-call" task?

AntCall effectively creates a new Ant instance. Properties and
references set within the call won't be visible after the call
returns, and targets executed before the call might be executed
again within the call. It's very different from having a target
as a dependency. Replacing one with the other has all sorts of
ramifications.

-- Niklas Matthies

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


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

=0A=0A=0A      
--0-1816305784-1282237165=:15814--