Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 57707 invoked from network); 3 Dec 2009 22:12:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Dec 2009 22:12:15 -0000 Received: (qmail 60876 invoked by uid 500); 3 Dec 2009 22:12:14 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 60792 invoked by uid 500); 3 Dec 2009 22:12:14 -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 60782 invoked by uid 99); 3 Dec 2009 22:12:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2009 22:12:14 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [68.142.200.147] (HELO web30804.mail.mud.yahoo.com) (68.142.200.147) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 03 Dec 2009 22:12:04 +0000 Received: (qmail 47162 invoked by uid 60001); 3 Dec 2009 22:11:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1259878302; bh=LFrH20f/4OqWZNwsSgEx+JznZZIsMfvanNxNjUOykak=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=futIVgF2OXB1QnC7gWKstid4Gael7ioLBx4CCQ8y8EybbwMJvnaKH8V1YXbR+HhclAjl96aPCnoLTnK2YZcz+I26YcnSN7nJFX6aLsFr+2Iiw0wJkid0h8QfxUMvofAwRSAvTr/x6dHQ6scd2AtA0gE4hmLldMEPiWKZDb84xQk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=pCkUCj4/tsG5hfZal0kH0bLttDE25htr8tykAoc/263gCGHUl1OPzKQdsR8TiVlkWEoKqM2nHlZnwImlpA/GrJH8uD/ATXu/mfU47SbvRTys9CUA/1Hwd3AeqikRfmAxQV4/UtBa6nXUMWm6Wnr4cvZGSdtnn86wpfAEtb69Vus=; Message-ID: <660474.47104.qm@web30804.mail.mud.yahoo.com> X-YMail-OSG: exxf1qkVM1lJAm1SZ7hCAyH8CSd040ZIWorc8Qgadh7qRwBXh3GqZ3JQmjmX_VI1DBzWRG8RdmR3q.YQSw8LOoKiRFNUcXH6y9JVJfcfaddPSxmRNhSZV7a5kgLVp.TP24Tp5tCRKfFPmVZwuHC0u09w9gck96YnGi9vbi5u3wSE11_5sr40SXByh6Mc82fOw7o07E25uftCSBEBrSiV5.Y9HMINzWmtcWy73cAGDyCRbZavIWmqzKDn9zQUq6RdsEsq4790IssMbaFj8.H_37FzEJEt1HgQDBkKg7FPaTGdHVNQiZbmUSja1QoKVpN7bH.RViJeM0wgZgVeZAq7BGxU7YQaCcHESQB8CLzG3XALTPWveHfkOpyWOsgXi.31bc.FeEs47tWPPbEyHtJ3uv6vJtuz6vzdLYHzIl27Kh33K29R4u0K3g1eSkDX2s.QJmPAV7ccfsXA9y_hAGdQu3_LDjYYj4XYb8I_bMsfrFLG0D6iNArvgy6.V5a1AR0oToS8luXjipFyOEHCTi5A.rViqa9df3dn2u.G3ik75xwBjHeHncz5dq4q.pvC9z1HGB8AjyrE.iBPAo4MJW4B94Gzq.CM3CjF.5mSmP.2JtrA38v4B476VqAiIlaRwtmXNAO9pWiCPJsrc1Dl_fbXk3itmlxyhWfSDhtoHPTTS_JBIF_kp3fqvodRDg-- Received: from [217.136.26.213] by web30804.mail.mud.yahoo.com via HTTP; Thu, 03 Dec 2009 14:11:42 PST X-Mailer: YahooMailRC/211.6 YahooMailWebService/0.8.100.260964 References: <26633391.post@talk.nabble.com> Date: Thu, 3 Dec 2009 14:11:42 -0800 (PST) From: Maarten Coene Subject: Re: Resolving the latest version when it has the same rev To: ivy-user@ant.apache.org In-Reply-To: <26633391.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org You can accomplish this by setting the changingPattern to ".*-LATEST" on your resolver in your settings.xml. Cfr. http://ant.apache.org/ivy/history/latest-milestone/settings/resolvers.html#common Maarten ----- Original Message ---- From: fnord To: ivy-user@ant.apache.org Sent: Thu, December 3, 2009 10:21:45 PM Subject: Resolving the latest version when it has the same rev We're using a system where the continuous integration server is monitoring trunks, and when they update it is publishing the artifacts with a revision of LATEST. I've been digging through the docs for a while now, and remain confused about what would be the best way to make sure that when I call ivy:resolve, it's actually checking the artifact rather than just the revision name to pull in the latest artifacts from the repository. Anyone have a best practice for doing this? thanks, fnord -- View this message in context: http://old.nabble.com/Resolving-the-latest-version-when-it-has-the-same-rev-tp26633391p26633391.html Sent from the ivy-user mailing list archive at Nabble.com.