Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 14883 invoked from network); 29 Feb 2008 11:31:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Feb 2008 11:31:59 -0000 Received: (qmail 49383 invoked by uid 500); 29 Feb 2008 11:31:54 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 49338 invoked by uid 500); 29 Feb 2008 11:31:53 -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 49327 invoked by uid 99); 29 Feb 2008 11:31:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 03:31:53 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com designates 72.14.204.228 as permitted sender) Received: from [72.14.204.228] (HELO qb-out-0506.google.com) (72.14.204.228) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 11:31:17 +0000 Received: by qb-out-0506.google.com with SMTP id z1so5528594qbc.10 for ; Fri, 29 Feb 2008 03:31:26 -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:mime-version:content-type; bh=GUwJU5t72NUBLufeOnirIieeI844f3svUqd9o/De1H8=; b=AlJjrJER1R6dSSCss4FBA8LaqbZrruX7DdNOQb0UtamSllkGxnLdMTnA8nfP0Lepgt9deOTC0isiIdjuNIDTJunVEGZAVETwKQXbKpIlZIYx5Ftkyrty0n88k/dlbrlleialiGIGJjvsMoMRwtD6cQGxosNC7TebMaFobfVfoz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=oRXAj2yNSnCU3z3/lKWMmV654Zh66NYxDHLlTVij9gszUFeNNbiq5LtI6jnk/yuCf9J3VOgWu4J8z/9C/wsEsOQ0zcqDsPqcc4I9jpJrSAip78P0NPySlM/byLYQYTp0lNRkp45rJ9JDacirn4MpsLxELv1Z3FqUxwqySvcXv3Q= Received: by 10.140.193.16 with SMTP id q16mr5565963rvf.109.1204284686106; Fri, 29 Feb 2008 03:31:26 -0800 (PST) Received: by 10.141.171.19 with HTTP; Fri, 29 Feb 2008 03:31:26 -0800 (PST) Message-ID: <635a05060802290331j681e417xaa1c2166debe8120@mail.gmail.com> Date: Fri, 29 Feb 2008 12:31:26 +0100 From: "Xavier Hanin" To: "Ant Developers List" Subject: Fixing some naming inconsistencies in Ivy MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9822_17139836.1204284686090" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_9822_17139836.1204284686090 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. 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? Xavier -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_9822_17139836.1204284686090--