Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 90426 invoked from network); 14 Feb 2008 10:41:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2008 10:41:35 -0000 Received: (qmail 57143 invoked by uid 500); 14 Feb 2008 10:41:27 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 57107 invoked by uid 500); 14 Feb 2008 10:41:27 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 57098 invoked by uid 99); 14 Feb 2008 10:41:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2008 02:41:27 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of alexei.zakharov@gmail.com designates 209.85.146.176 as permitted sender) Received: from [209.85.146.176] (HELO wa-out-1112.google.com) (209.85.146.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2008 10:40:56 +0000 Received: by wa-out-1112.google.com with SMTP id k22so609768waf.18 for ; Thu, 14 Feb 2008 02:41:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=08RP7Zr2qEF0zOF4tVKav7nNXBjWK7k+x1CGXwAj/JY=; b=L1b+QUX26Notfoa2wCkf/HZEVLnzdyrCn/OmHqWRm7AngN/vxvWBy4KTmKXpnACUUq+iwMON4Fsyv6aqcL+4dtlaKQmQ5S1kOKFRgAedp5Jp0Bmx3VBubaX1dn80kNS5rIIvZ5TSyiypsuRojZxslHRT18AT7JtsRMqYoVNDA6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FXAbzajrjVTOi54HApIMEEGXAKYjUYoh2G2t+qx6Psz9lE+4rUe9k1USNijR5nNuKkrjn67QFwMRHuQqwlv79RjXO1zkghK5PmPFX1bhWTU+CwDYm3ayyI2G4btZ9YibmpHCXtharTBnABpmCf1Dvd4FEgWBTI11X4hlghGlxZQ= Received: by 10.114.12.9 with SMTP id 9mr1335731wal.23.1202985665163; Thu, 14 Feb 2008 02:41:05 -0800 (PST) Received: by 10.114.198.16 with HTTP; Thu, 14 Feb 2008 02:41:05 -0800 (PST) Message-ID: <2c9597b90802140241m2c8eea3y4a1eb2b969d1200f@mail.gmail.com> Date: Thu, 14 Feb 2008 13:41:05 +0300 From: "Alexei Zakharov" To: dev@harmony.apache.org Subject: Re: [build] ant target naming consistency In-Reply-To: <200802140908.m1E98rKC008587@d12av04.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3b3f27c60802131932ia2ef362mcce8a533cdc5c85d@mail.gmail.com> <200802140908.m1E98rKC008587@d12av04.megacenter.de.ibm.com> X-Virus-Checked: Checked by ClamAV on apache.org +1, make sense IMO. I never liked this mix of '-' and '_' . Regards, Alexei 2008/2/14, Mark Hindess : > > On 13 February 2008 at 21:32, "Nathan Beyer" wrote: > > Does anyone object to normalizing the names of the Ant targets? The > > mixed use of '-' and '_' is starting to push me over the edge. As an > > example, here's the targets available in the top-level of the > > federated build. > > > > build-all build complete implementation > > bundle_src assemble source snapshot > > default setup and build complete implementation > > make-snapshot setup and build complete src + binaries set > > populate_source checkout the class library and VM source trees > > reset removes vm and classlib dirs and resets > > > > I'd like to just use '-' across the board. > > > +1 > > As a low priority, we should also try to be consistent in using names starting > with '-' for all targets that don't form part of the api and including good > descriptions for those that do. > > > > We can maintain the previous targets for a while via redirects and put > > in some deprecation statements. > > > I would be inclined to have the old targets just fail with a message > containing the new target name. That is, force people to change rather > than letting the depreciated targets work by calling the new targets automatically. > > Regards, > > Mark. > > >