Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 43972 invoked by uid 500); 20 Jun 2001 17:27:43 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 43306 invoked from network); 20 Jun 2001 17:27:15 -0000 Message-ID: <4E7888D4F219E145B6F81E5D3049E3BF1B10CB@scmail01.arsin.com> From: Peter Vogel To: "'ant-user@jakarta.apache.org'" Subject: RE: Competition to Ant Date: Wed, 20 Jun 2001 10:27:16 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N It's more a matter of "complex" as Peter D. suggested, and, in most of the cases where there is "complexity" to deal with, it is a matter of the organizational complexity (multiple organizational projects contributing to one or more products) and a need to present a *very* simple face to the developers who use it. For example, here's a project build file (with some expository comments removed for e-mail brevity): ]> &property; &targets; Behind this, of course, are the property.xml and target.xml files which are responsible for setting up a standard environment and target set to support the *product* build. It should be noted that in order to make this work as cleanly as it does I needed to patch ant in a couple of ways: 1. expand properties in the target element's depend attribute's value. 2. fix to use it's "dir" value instead of the tar's basedir 3. add the "outputproperty" attribute to to store the output of a command in a property. And we wrote a custom task to handle building Solaris Packages from what we built. It would be even cleaner with a :-) -Peter > -----Original Message----- > From: Larry V. Streepy, Jr. [mailto:streepy@healthlanguage.com] > Sent: Tuesday, June 19, 2001 9:26 AM > To: ant-user@jakarta.apache.org > Subject: Re: Competition to Ant > > > Probably shouldn't even ask this, but what do you consider a "large" > project? I'm managing a project with hundreds of source > files, creation > of a dozen jar files, EJB deployment, IIOP support, some platform > specific behavior for creating distribution media and I have not hand > any significant problems with ant. > > Jesse Tilly wrote: > > > > heh. I think Peter V. would disagree with that "suitable for large > > projects" statement....as would I. > > > > MrT > > > > > -----Original Message----- > > > From: Jim Jackl-Mochel [mailto:jmochel@foliage.com] > > > Sent: Tuesday, June 19, 2001 10:33 AM > > > To: ant-user@jakarta.apache.org > > > Subject: RE: Competition to Ant > > > > > > > > > > > > I don't know if they are truly competition but there are jmk > > > and jmake. > > > Both are small and clean but don't have ANT's suitability > for large > > > projects. > > > > > > > > > Jim JM > > > > -----Original Message----- > > > > From: Shaikh, Mehmood [mailto:Mehmood.Shaikh@ccra-adrc.gc.ca] > > > > Sent: Tuesday, June 19, 2001 10:36 AM > > > > To: 'ant-user@jakarta.apache.org' > > > > Subject: Competition to Ant > > > > > > > > > > > > Is anyone aware of any competition to Ant as a build tool? > > > > > > > > Thanks > > > > > > > > Mehmood > > > > > -- > Larry V. Streepy, Jr. > Chief Technical Officer and VP of Engineering > > Health Language, Inc. -- "We speak the language of healthcare" > > 970/626-5028 (office) mailto:streepy@healthlanguage.com > 970/626-4425 (fax) http://www.healthlanguage.com >