Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 20758 invoked from network); 9 Oct 2008 23:52:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2008 23:52:18 -0000 Received: (qmail 93783 invoked by uid 500); 9 Oct 2008 23:52:16 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 93762 invoked by uid 500); 9 Oct 2008 23:52:16 -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 93751 invoked by uid 99); 9 Oct 2008 23:52:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 16:52:16 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=DNS_FROM_OPENWHOIS,DNS_FROM_SECURITYSAGE,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 23:51:12 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Ko5IJ-0003R6-Ge for ivy-user@ant.apache.org; Thu, 09 Oct 2008 16:51:47 -0700 Message-ID: <19909555.post@talk.nabble.com> Date: Thu, 9 Oct 2008 16:51:47 -0700 (PDT) From: buzzterrier To: ivy-user@ant.apache.org Subject: resolver return wrong artifact of status MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: terry.jeske@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org I published two revisions of the same artifact with a release and a milestone statuses. In my repository I have: c:\svnrepos\foo.bar\coreTools\milestone-1.1 coreTools-milestone-1.1.jar ivy-milestone-1.1.xml ivy-milestone-1.1.xml contains: and c:\svnrepos\foo.bar\coreTools\release-1.1 coreTools-release-1.1.jar ivy-release-1.1.xml ivy-release-1.1.xml contains: So the generated ivy files are correctly recording the status. When I resolve coreTools from another project with latest.milestone, ivy returns the release-1.1 artifact. Below is the debug output. The resolver finds both revisions, but decides to use the release. Any ideas? Getting list for svn://subversion/ivy/aero.blue/coreTools/ [revision=-1] Adding SVN user/pass authentication found 2 resources found revs: [milestone-1.1, release-1.1] Resolving resource for svn://subversion/ivy/aero.blue/coreTools/milestone-1.1/ivy-milestone-1.1.xml [revision=-1] Resource found at svn://subversion/ivy/aero.blue/coreTools/milestone-1.1/ivy-milestone-1.1.xml, returning resolved resource Resolving resource for svn://subversion/ivy/aero.blue/coreTools/release-1.1/ivy-release-1.1.xml [revision=-1] Resource found at svn://subversion/ivy/aero.blue/coreTools/release-1.1/ivy-release-1.1.xml, returning resolved resource shared: found md file for aero.blue#coreTools;latest.milestone => svn://subversion/ivy/aero.blue/coreTools/release-1.1/ivy-release-1.1.xml (release-1.1) parser = ivy parser no ivy file in cache for aero.blue#coreTools;release-1.1: tried C:\tools\ivy\settings\ivy-cache\aero.blue\coreTools\ivy-release-1.1.xml downloading svn://subversion/ivy/aero.blue/coreTools/release-1.1/ivy-release-1.1.xml ... shared: downloading svn://subversion/ivy/aero.blue/coreTools/release-1.1/ivy-release-1.1.xml to C:\tools\ivy\settings\ivy-cache\aero.blue\coreTools\ivy-release-1.1.xml.original.part Getting file for user webapp from svn://subversion/ivy/aero.blue/coreTools/release-1.1/ivy-release-1.1.xml [revision=-1] to C:\tools\ivy\settings\ivy-cache\aero.blue\coreTools\ivy-release-1.1.xml.original. -- View this message in context: http://www.nabble.com/resolver-return-wrong-artifact-of-status-tp19909555p19909555.html Sent from the ivy-user mailing list archive at Nabble.com.