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 16580 invoked from network); 11 Apr 2000 17:21:06 -0000 Received: from unknown (HELO mailhost01.reflexnet.net) (64.6.192.82) by locus.apache.org with SMTP; 11 Apr 2000 17:21:06 -0000 Received: from SUCCUBUS ([64.6.208.156]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 11 Apr 2000 10:20:46 -0700 Message-ID: <013c01bfa3da$44ec7b50$9cd00640@SUCCUBUS> Reply-To: "Scott M Stark" From: "Scott M Stark" To: References: <852568BE.00496A7A.00@d54mta04.raleigh.ibm.com> Subject: Re: Release plan Date: Tue, 11 Apr 2000 10:20:44 -0700 Organization: Displayscape.com MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > Suggestions? Volunteers? > > - Sam Ruby > I'll volunteer, but first let me ask a question about exactly what the scope of Ant is supposed to be. Let me put this question in the context of a recent gnumake to Ant porting effort. The one target type that I could not port to Ant without extensive custom taskdefs was the ability to define a jar of classes target in terms of its source dependencies. This turns out to be nontrivial because of inner classes, rmi stubs, source generated from JavaCC grammars, etc. I was able define a scheme that handled all these issues using gnumake pattern rules and its internal functions. Its complicated and fragile however. I'm not saying Ant should or should not support this type of target at its core. I'm asking what the scope of the core Ant functionality should be. Scott