Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 24480 invoked from network); 11 Feb 2008 18:44:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Feb 2008 18:44:33 -0000 Received: (qmail 47342 invoked by uid 500); 11 Feb 2008 18:44:26 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 47328 invoked by uid 500); 11 Feb 2008 18:44:26 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 47319 invoked by uid 99); 11 Feb 2008 18:44:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2008 10:44:26 -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 209.85.198.191 as permitted sender) Received: from [209.85.198.191] (HELO rv-out-0910.google.com) (209.85.198.191) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2008 18:43:54 +0000 Received: by rv-out-0910.google.com with SMTP id k15so3312306rvb.40 for ; Mon, 11 Feb 2008 10:44:02 -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:references; bh=Cow/ab/DUmr//P7m/1IcUlXiMHSHWAOlkmcRzfCGAlI=; b=BCD0Y5wt3USgxHtCoNwAV2HM4Z8iulQM+gw8wJXWA5nMmZpz7iHumDxymuiJS7e2ywlcLjaqIWZljy4Yofn12Wq39WQpgbwQtJa+kmuchbDPN2qMBVkUvGPdYn+J5gMe2Vn4S02Vg6SozipBjy0Ev/Ai584OozLtTJoTrjCKcTI= 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:references; b=XtXMhAep25iYEio96ENjqbmmF7Dn2YUmoJyyWfstjhbLuAN5GHMZ0W3iBD/G1s3GWZ02M+ZEZP6h2gLrh7f0WTF6jqkj5iaS7sJt2NNgWOQ/baj2dRRFnCqsCYSFYYEDYLYmOzXPQeP6gxRwtufNqur/ufju58WiJiMce3R2NEw= Received: by 10.140.179.25 with SMTP id b25mr227963rvf.117.1202755442492; Mon, 11 Feb 2008 10:44:02 -0800 (PST) Received: by 10.141.171.19 with HTTP; Mon, 11 Feb 2008 10:44:02 -0800 (PST) Message-ID: <635a05060802111044o77e4b64bu5b15852f17ef586e@mail.gmail.com> Date: Mon, 11 Feb 2008 19:44:02 +0100 From: "Xavier Hanin" To: ivy-user@ant.apache.org Subject: Re: install task bug? In-Reply-To: <745B9EDF57802349B13F90E4E0B4B86C3B92428AC5@HOUEXCH012.corp.halliburton.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25153_17992210.1202755442480" References: <745B9EDF57802349B13F90E4E0B4B86C3B92428AC5@HOUEXCH012.corp.halliburton.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_25153_17992210.1202755442480 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Feb 11, 2008 6:07 PM, Shawn Castrianni wrote: > I am using the install task to copy builds of my modules from one resolver > to another, which is what it was designed to do. However, I have noticed > that it appears to be dependent on the defaultResolver in the settings file. > I think this is a bug since the install task takes as attributes the from > and to resolver. The from resolver should be used to find the module > instance to copy from (not the defaultResolver) and the to resolver should > be used to locate the destination of where to copy the module instance to. > Therefore, if I specify the revision of "latest.testing" in my install > task and a from resolver of "testing", it should find the latest revision of > my testing modules in the testing resolver. However, it is not finding the > latest one. I changed my defaultResolver in my settings file to be > "testing" and then it started to work properly. I changed it back and it > failed again. That tells me that the install task is using the value of > defaultResolver somehow. Am I understanding things correctly? By the way, > if I change my revision spec in the install task to be a specific revision > number in the "latest" resolver, it works fine. The bug is only when I use > the latest.XXXX method. According to what you experience, this is clearly a bug. I'm surprised no unit test catched it before. Could you please open a JIRA? Xavier > > > --- > Shawn Castrianni > CM Lead Architect > Landmark > Halliburton Drilling, Evaluation and Digital Solutions Building 2 > 2101 City West Blvd. > Houston, TX 77042 > Work: 713-839-3086 > Cell: 832-654-0888 > Fax: 713-839-2758 > > ---------------------------------------------------------------------- > This e-mail, including any attached files, may contain confidential and > privileged information for the sole use of the intended recipient. Any > review, use, distribution, or disclosure by others is strictly prohibited. > If you are not the intended recipient (or authorized to receive information > for the intended recipient), please contact the sender by reply e-mail and > delete all copies of this message. -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_25153_17992210.1202755442480--