Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <3A6CC74E.493B6625@progress.com>
Date: Mon, 22 Jan 2001 18:50:38 -0500
From: "Bill Burton" <billb@progress.com>
Organization: Progress Software Corporation
MIME-Version: 1.0
To: ant-dev@jakarta.apache.org
Subject: Re: long command lines from execon with parallel=true
References: <Pine.LNX.4.21.0101231003200.29093-100000@marni.otago.ac.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

Mariusz Nowostawski wrote:
> 
> On Mon, 22 Jan 2001, Dan Christopherson wrote:
> > Under ant 1.2 and ant 1.3 I'm using the execon task to fire off a build of
> > a pile of JSPs (under WinNT). this results in a very long command line
> > that will not execute.
> >
> > I've made a local change to the 1.2 sources to add a 'batch' attribute to
> > the execon task (telling it how many source files to pass per batch
> > execution of the command). Should I submit this patch?
> 
> Sounds all right to me. Some of the underlying executable programs may
> also expect limited number of arguments, so your patch would make that
> easier to use as well.

I think it would be preferable to specify the maximum length of the
command rather than the number of arguments.  Since length of paths can
vary wildly, there's no guarantee a certain number of arguments won't
still be too long in some cases.  

-Bill Burton

> > Alternatively, is there another way to accomplish the same means with
> > the normal functionality?
> 
> You can always use:
> * parallel=false, to make single argument per call (slow)
> * split single <execon> into several ones making partitioning of argments
>   by explicit arbitrary matching (not nice in general case)
> 
> best regards
> Mariusz