Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 13538 invoked from network); 22 Jan 2001 21:07:26 -0000 Received: from marni.otago.ac.nz (root@139.80.75.248) by h31.sny.collab.net with SMTP; 22 Jan 2001 21:07:26 -0000 Received: from localhost (mariusz@localhost) by marni.otago.ac.nz (8.9.3/8.9.3) with ESMTP id KAA29204 for ; Tue, 23 Jan 2001 10:07:23 +1300 Date: Tue, 23 Jan 2001 10:07:23 +1300 (NZDT) From: Mariusz Nowostawski To: ant-dev@jakarta.apache.org Subject: Re: long command lines from execon with parallel=true In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N 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. > 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 into several ones making partitioning of argments by explicit arbitrary matching (not nice in general case) best regards Mariusz