From dev-return-82522-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Sat Mar 29 19:56:19 2008 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 79710 invoked from network); 29 Mar 2008 19:56:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Mar 2008 19:56:19 -0000 Received: (qmail 44045 invoked by uid 500); 29 Mar 2008 19:56:18 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 43993 invoked by uid 500); 29 Mar 2008 19:56:18 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 43982 invoked by uid 99); 29 Mar 2008 19:56:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Mar 2008 12:56:18 -0700 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 sbailliez@gmail.com designates 72.14.220.158 as permitted sender) Received: from [72.14.220.158] (HELO fg-out-1718.google.com) (72.14.220.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Mar 2008 19:55:37 +0000 Received: by fg-out-1718.google.com with SMTP id 22so1842186fge.22 for ; Sat, 29 Mar 2008 12:55:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=6ejOV9SujsznSrNb+XnGf2Up9R9/6fA+NnVDOF4GXHU=; b=CE/LpYL5BRNzK47RFPoJfwFZLcqlR3TTupXYKefx6IAMrUYFHOZv0ODTs+KcxBw0gGkUEcfKuYrefM49cu94iE08mjaMwqByxA5XCreAX73IbncBn1Q8+IIMvsiG7nieQWweLLAxvYqegWbUTfZ2+a9FtbY9ril49FbVzWPhkdQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Dlqa5qdi7NrmUmrLH4y+1tLi6ieajSoVFuwio90HpliOs9htKnp57mMvyCYt6Rrl8liWN8t4v94QRXkVkwXLkR5Wt9FZu3njvVRsE4ROVBbJrh1hEw/ub5BfJW2VPzVXfL5OYCezPz6XJjwgpIUe5/ogWERmsMlQqc+0vvtvSBY= Received: by 10.82.146.10 with SMTP id t10mr11312072bud.6.1206820547194; Sat, 29 Mar 2008 12:55:47 -0700 (PDT) Received: from ?192.168.1.100? ( [81.71.88.48]) by mx.google.com with ESMTPS id u14sm5999317gvf.1.2008.03.29.12.55.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 29 Mar 2008 12:55:46 -0700 (PDT) Message-ID: <47EE9EB3.9060007@gmail.com> Date: Sat, 29 Mar 2008 20:55:31 +0100 From: Stephane Bailliez User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Ant Developers List Subject: Re: Fixing some naming inconsistencies in Ivy References: <635a05060802290331j681e417xaa1c2166debe8120@mail.gmail.com> <635a05060803290209l65c17418p4c4beb897e78da@mail.gmail.com> In-Reply-To: <635a05060803290209l65c17418p4c4beb897e78da@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Xavier Hanin wrote: > Just pinging about this e-mail, I've had no answer so far, I think I can't > make the choice alone, and we need to deal with that question before > 2.0final to close IVY-297. So, anyone has an opinion about this: > > On Fri, Feb 29, 2008 at 12:31 PM, Xavier Hanin > wrote: > >> Hi, >> >> As reported by IVY-297, Ivy suffers from some name inconsistencies and >> strange attribute names. Ivy 2.0 is a good opportunity to fix some of >> them, since I think we can afford some more deprecation warnings. >> >> So I'd like to fix IVY-297 by marking allownomd as deprecated, and >> providing a descriptor="required | optional" attribute. >> >> To go further, we could rename the attribute skipbuildwithoutivy in >> buildlist in skipbuildwithoutdescriptor, or even better change it to >> buildwithoutdescriptor="skip | fail | warn | tail | head", which wold make >> it both more readable and more powerful. >> s/buildwithoutdescriptor/missing-descriptor ? onMissingDescriptor ? imnotgenerallyabigfanofwordsgluedtogetherwithoutseparator when it it's more then 2 words (onchange, on..) OtherwiseThereIsCamelCaseButThisIsUglyTooForXml >> Another area where the name 'ivy' is used to talk about module descriptors >> in general is patterns. This lead to some strange settings, where you give >> an 'ivy' pattern to tell where the poms are. In this case I think we could >> support both 'ivy' and 'descriptor' (for resolver patterns for instance), >> since the use case for ivy files is still predominant, so I don't think >> deprecating the old name would really be better. >> >> So, what do you think about these changes? >> I guess if you want to make it it's probably 2.0 or never... there's already a lot of deprecated right now and it will get more difficult to push them in later. After all it's a 2.0 -- stephane --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org