On 30/05/2010 11:27 AM, Bruce Atherton wrote:
I realized that I screwed up two ways with this answer. First, my
intention was 'resultproperty="${result}"' rather than as written. But
this won't work either because the PropertyHelper will just give back
the literal string when the setter is c
On 27/05/2010 2:04 AM, jan.mate...@rzf.fin-nrw.de wrote:
Please have a look at https://svn.apache.org/repos/asf/ant/sandbox/autoconf/
Maybe that could help.
But he still has a call to the setter even if it is autoconfed.
Note that setting spawn and resultproperty are mutually exclusive. If
Please have a look at https://svn.apache.org/repos/asf/ant/sandbox/autoconf/
Maybe that could help.
Jan
>-Ursprüngliche Nachricht-
>Von: Antoine Levy-Lambert [mailto:anto...@gmx.de]
>Gesendet: Mittwoch, 26. Mai 2010 17:31
>An: Ant Users List
>Betreff: Re: New ANT task c
Hello Shawn,
I hope some one has a useful answer for this.
Original-Nachricht
> Datum: Wed, 26 May 2010 10:03:30 -0500
> Von: Shawn Castrianni
> An: "\'Ant Users List\'"
> Betreff: New ANT task coding guideline
> Therefore, I propose that
I would like to propose a new ANT task coding guideline. I frequently need to
allow my users to customize the ANT build via a build.properties file.
Therefore, a lot of my ANT task usage has placeholders for the various
different ant task attributes with variables, ${}. The problem is
