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 77435 invoked from network); 28 Dec 2000 13:53:28 -0000 Received: from moutvdom00.kundenserver.de (195.20.224.149) by h29.sny.collab.net with SMTP; 28 Dec 2000 13:53:28 -0000 Received: from [195.20.224.220] (helo=mrvdom04.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 14BdUk-0005GO-00; Thu, 28 Dec 2000 14:53:26 +0100 Received: from p3ee2dcb7.dip.t-dialin.net ([62.226.220.183] helo=nexolution.de) by mrvdom04.kundenserver.de with esmtp (Exim 2.12 #2) id 14BdUg-00029M-00; Thu, 28 Dec 2000 14:53:23 +0100 Message-ID: <3A4B4531.EBA41822@nexolution.de> Date: Thu, 28 Dec 2000 14:50:41 +0100 From: marco struck X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: ant-user@jakarta.apache.org, ant-dev@jakarta.apache.org Subject: Re: Fw: Problem using script task References: <20001226192045.7735.qmail@web117.yahoomail.com> <082601c06f76$28e5d970$020a0a0a@alsatian> <3A49FE99.313D9903@machturtle.com> <095c01c070ca$a11eaa20$020a0a0a@alsatian> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: h29.sny.collab.net 1.6.2 0/1000/N Jason, I absolutely agree with you. ANT is very nice to handle classes, jars, zips, cvs and so on. But that was just the first step. People have found with ANT an easy way to handle their project structures. The first impression of ANT - also to me - is: ANT is the solution for all our problems. But the second one: We need more control (as Jason described). After some weeks of discussion about the introduction of ANT in my company, we came to the issue, that we have to write own tasks to handle the shortcomings of ANT ......but I think, that could not be the right way. A task should be a kind of component which encapsulate complex functionality and should be uses as kind of black box in build files. I think: Scripting should be a core feature of ANT2. Jason Rosenberg wrote: > What I see as really great about Ant is that it provides > a very clean, platform-independent framework for building > platform-independent software. > > In addition to the obvious platform independent advantages > of working with java type stuff, it also hides the details of > dealing with file-system stuff, which is usually very platform > specific. Issues such as checking relative time-stamps, > and converting '\' to '/', etc. > > Also, it has a very clean target/dependency/task description > frame work, which is nicely extensible and customizable. > > But it has some fundamental short-comings. I am formulating > a more formal argument on this, which I will post later. > > Some key points: > > Ant is already a programming language; it gets interpreted > directly by the virtual machine that is 'org.apache.tools.ant.Main.main'. > > It already includes fundamental programming constructs, such > as variable declarations (e.g. ), conditional execution > (e.g. ,,) and sub-routine calls (e.g. > ,,). > > Those fundamental programming constructs have fundamental > shortcomings, which severly limit one's ability to construct > simple scripts which can be applied as a library of parameterized > templates for doing a long list of similar tasks. > > There are some simple extensions to Ant which would rescue > these short-comings. > > The