On Thu 2010-08-19 at 09:59h, Vimil Saju wrote on user:
> I read about the new macrodef task which can be used create a custom
> composite task by combining other tasks together. Using the macrodef
> task instead of antcall cant we overcome the performance overhead
> and the property visibility issu
; visibility issues with antcall?
>
Certainly, aside from the fact that macrodef is not really that new, having
been released with Ant 1.6 IIRC. ;)
-Matt
> --- On Thu, 8/19/10, Knuplesch, Juergen wrote:
>
> From: Knuplesch, Juergen
> Subject: AW: Conditional target problem
>
wrote:
From: Knuplesch, Juergen
Subject: AW: Conditional target problem
To: "Ant Users List"
Date: Thursday, August 19, 2010, 8:03 AM
Antcallback gives back some props you define
-Ursprüngliche Nachricht-
Von: Niklas Matthies [mailto:ml_ant-u...@nmhq.net]
Gesendet: Mittwoch,
Antcallback gives back some props you define
-Ursprüngliche Nachricht-
Von: Niklas Matthies [mailto:ml_ant-u...@nmhq.net]
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 a
I use the from ant-contrib combined with antcall or antcallback to have
more flexibility on calling targets.
I use properties like ${nocvs} to not use CVS, even when the target is executed
(again using or unless)
I have unless properties for CVS, junit, javadoc, compile .
In your c
