From dev-return-84057-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Mon Mar 09 17:54:17 2009 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 29012 invoked from network); 9 Mar 2009 17:54:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Mar 2009 17:54:17 -0000 Received: (qmail 97440 invoked by uid 500); 9 Mar 2009 17:54:15 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 97397 invoked by uid 500); 9 Mar 2009 17:54:15 -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 97386 invoked by uid 99); 9 Mar 2009 17:54:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 10:54:15 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gscokart@gmail.com designates 209.85.218.175 as permitted sender) Received: from [209.85.218.175] (HELO mail-bw0-f175.google.com) (209.85.218.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 17:54:07 +0000 Received: by bwz23 with SMTP id 23so1188711bwz.28 for ; Mon, 09 Mar 2009 10:53:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=ZmyElvLx0ccfZcCmlCfEipDY23utQcDf7rINg7SBGFo=; b=egovn2EoHCQAdAP9NnxJ18HylROXmk1N7b4iXqtRJknlC8n29s2aDJLUqLaT5Y7da2 9w374i57rzYfrWrqZxI+FI7ZRQ1mpZyklb+w2WUkZmcjwFoSRHmlJiwJSHgriSlIcX3S 0jWfn2t8XXJDZgVwPt5qYA3ekgmHDma0LTpm4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ovF9ExOsxNFf8+H1eFGfulUyHM/uCL6RP9i45v1o1dV1x90E2v737Mea1oyALNO3sJ 9aN8BLH4Vv/Xi5bJ63E7Hg8Sqb6iZj8TOxRIw3TDwo9vYRzWVlTkjRtR0Ol/eBXsPhp8 cwMDYFvRCdfkdCMK5+sDDis4qFErsERPz/4J0= MIME-Version: 1.0 Received: by 10.223.107.199 with SMTP id c7mr4721200fap.31.1236621226964; Mon, 09 Mar 2009 10:53:46 -0700 (PDT) In-Reply-To: <572104.8871.qm@web30805.mail.mud.yahoo.com> References: <572104.8871.qm@web30805.mail.mud.yahoo.com> Date: Mon, 9 Mar 2009 18:53:46 +0100 Message-ID: Subject: Re: changing Ivy retrieve behaviour From: Gilles Scokart To: Ant Developers List Content-Type: multipart/alternative; boundary=001636c5b84df476190464b35007 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5b84df476190464b35007 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I think failing the build is indeed the best aproach. But I fear some build that might be broken. Isn't it? I'm also wondering if it is not possible to have warning in the retrieve task when some kind of patterns are used. Gilles Scokart 2009/3/9 Maarten Coene > > Hi, > > I would like to change the Ivy retrieve behaviour regarding conflict > handling when multiple artifacts are retrieved to the same file. > At the moment, Ivy has some kind of retrieve-conflict-manager which selects > the "best" artifact, based on the revision of the conflicting modules. > This doesn't work when multiple artifacts of the same module is retrieved > to the same file. At the moment, this is causing problems with the maven > source/javadoc artifacts which are sometimes retrieved instead of the > class-files. > > I would like to change this so that Ivy throws an error if multiple > different artifacts map to the same file. > Any objections? > > Maarten > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org > For additional commands, e-mail: dev-help@ant.apache.org > > --001636c5b84df476190464b35007--