From ivy-user-return-5432-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Mon Jun 15 05:19:40 2009 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 95137 invoked from network); 15 Jun 2009 05:19:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jun 2009 05:19:40 -0000 Received: (qmail 5877 invoked by uid 500); 15 Jun 2009 05:19:51 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 5827 invoked by uid 500); 15 Jun 2009 05:19:51 -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 5817 invoked by uid 99); 15 Jun 2009 05:19:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 05:19:51 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mads.tandrup@capgemini.com designates 194.11.253.100 as permitted sender) Received: from [194.11.253.100] (HELO SPFDEFRA01.capgemini.com) (194.11.253.100) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 05:19:39 +0000 X-IronPort-AV: E=Sophos;i="4.42,220,1243807200"; d="scan'208";a="148267081" Received: from unknown (HELO corpmx11.corp.capgemini.com) ([205.223.229.58]) by IRDEFRA-C650-01-D2-incoming.capgemini.com with ESMTP/TLS/RC4-MD5; 15 Jun 2009 07:19:18 +0200 Received: from CORPMAIL03.corp.capgemini.com ([205.223.229.250]) by CORPMX11 ([205.223.229.58]) with mapi; Mon, 15 Jun 2009 07:19:18 +0200 From: "Tandrup, Mads" To: "ivy-user@ant.apache.org" Date: Mon, 15 Jun 2009 07:19:17 +0200 Subject: SV: Chain resolver which uses the subresolver with the latest modification time Thread-Topic: Chain resolver which uses the subresolver with the latest modification time Thread-Index: AcnrZ0Ws4V3v3S2IR5CHsLrfkqrTyACEJ5Xi Message-ID: <719D82793F197440801C66B511B6255A1E72D06875@CORPMAIL03.corp.capgemini.com> References: <719D82793F197440801C66B511B6255A1E72D06874@CORPMAIL03.corp.capgemini.com>,<87d4991r6c.fsf@dell.crossleys.home> In-Reply-To: <87d4991r6c.fsf@dell.crossleys.home> Accept-Language: da-DK, en-US Content-Language: da-DK X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: da-DK, en-US Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Jim and all other Ivies Thanks for your quick reply. I've also looked at using latest.integration. Unfortunately I need to make = sure I get the correct branch resolved. Sometimes I need the latest build f= rom the 1.x branch (from whatever repository that is published to), and som= etimes I need the latest build from the 2.x branch. Best regards, Mads ________________________________________ Fra: Jim Crossley [jim@crossleys.org] Sendt: 12. juni 2009 16:07 Til: ivy-user@ant.apache.org Emne: Re: Chain resolver which uses the subresolver with the latest modific= ation time Hi Mads The only way I've found to force that behavior is to declare my dependency rev=3D"latest.integration" and of course, ensure that the status=3D"integration" for each of the modules you publish. This assumes you've set latest=3D"latest-time" in your resolvers, of course. HTH, Jim "Tandrup, Mads" writes: > Hello > > We have mayby a bit special situation where we have two repositories that= both contains the same modules with the same version numbers. They are how= ever build at different times. And we would like to receive the module with= the latest publication time. > But as far as I can see when the chain resolver resolves a specific versi= on, it always returns the first module with that revision? Is there any way= to make the chain resolver go through all the sub resolves and select the = module with the latest modifcation time? > > Best regards, > Mads > > Capgemini is a trading name used by the Capgemini Group of companies whic= h includes Capgemini Danmark A/S, a company registered in Denmark (number 2= 5606965) whose registered office is at ?rnegaardsvej 16 - 2820 Gentofte. > > > > > > > This message contains information that may be privileged or confidential = and is the property of the Capgemini Group. It is > intended only for the person to whom it is addressed. If you are not the = intended recipient, you are not authorized to > read, print, retain, copy, disseminate, distribute, or use this message o= r any part thereof. If you receive this message > in error, please notify the sender immediately and delete all copies of t= his message. Capgemini is a trading name used by the Capgemini Group of companies which = includes Capgemini Danmark A/S, a company registered in Denmark (number 256= 06965) whose registered office is at ?rnegaardsvej 16 - 2820 Gentofte. This message contains information that may be privileged or confidential an= d is the property of the Capgemini Group. It is=20 intended only for the person to whom it is addressed. If you are not the in= tended recipient, you are not authorized to=20 read, print, retain, copy, disseminate, distribute, or use this message or = any part thereof. If you receive this message=20 in error, please notify the sender immediately and delete all copies of thi= s message.