Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
To: ant-dev@jakarta.apache.org
Subject: Re: executing task for each file in file set
References: <00e401c0f401$2aa7d280$da76883e@viquity.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: 13 Jun 2001 15:15:04 +0200
Message-ID: <m3u21k4j3b.fsf@bodewig.bost.de>
Lines: 26
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Jose Alberto Fernandez <j_a_fernandez@yahoo.com> wrote:

>> Peter Vogel <pvogel@arsin.com> wrote:
>> > Except that "parallel" in the sense of execOn simply says that
>> > it's ok to provide the whole fileset to the command at once,
>> > rather than running the command for each file.
> 
> I think one of our worst decitions was to use "parallel" for the
> name of that attribute.

Mea culpa.

>> From: Stefan Bodewig [mailto:bodewig@apache.org]
>>
>> But you could only achieve the same as execon does if this string
>> representation is a space delimited list of absolute pathnames -
>> not the only reasonable choice for FileSet.toString().
> 
> I think this is the wrong approach because it puts too much
> dependency on surface syntax which can be OS dependant or what have
> you.

I still think that execon is worth a task of its own, even if there
was a foreach task in core.

Stefan