Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 83424 invoked by uid 500); 29 Mar 2001 16:47:06 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 83390 invoked from network); 29 Mar 2001 16:47:06 -0000 Message-ID: <20010329164707.67296.qmail@web13405.mail.yahoo.com> Date: Thu, 29 Mar 2001 08:47:07 -0800 (PST) From: Diane Holt Subject: Re: Another feature request?? To: ant-dev@jakarta.apache.org In-Reply-To: <3.0.6.32.20010330010550.00e31e40@alphalink.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N --- Peter Donald wrote: > I was thinking about this more when installing stuff. Under unixes you > usually have to go something like > > make clean; ./configure; make; make install > > It would be nice if the equivelent was translated into ants > > ant clean configure main install > > rather than 4 different invocations. However thats not possible now > because the user doesn't know the default target. Why wouldn't the supplied build-file just have the 'install' target run the 'clean', 'configure', and 'main' targets (either via s or the [new for Ant2, order-specifiable] "depends") and have 'install' be specified as the value for the "default" attr in ? Then the instructions for someone installing the software would simply be: 1. Unpack the file. 2. Run 'ant'. Ant doesn't need a built-in default target to make things easy for end-users -- and anyone writing an Ant build-file is going to have to learn lots of things that are far more complicated than specifying the default target in the tag. Diane ===== (holtdl@yahoo.com) __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/?.refer=text