Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 166 invoked from network); 3 May 2007 13:59:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 May 2007 13:59:51 -0000 Received: (qmail 84297 invoked by uid 500); 3 May 2007 13:59:56 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 84262 invoked by uid 500); 3 May 2007 13:59:56 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 84224 invoked by uid 99); 3 May 2007 13:59:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 06:59:56 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of gscokart@gmail.com designates 66.249.92.174 as permitted sender) Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 06:59:49 -0700 Received: by ug-out-1314.google.com with SMTP id y2so445243uge for ; Thu, 03 May 2007 06:59:27 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index; b=qTjncePwnHhXzhoDPsu6WOAhaMGf75fuiXCqE+/jb5/vXJqpVo1zfnroWQ7uGhtTzrnVrNi3erY6B8Fn2qZdHtxNTMuf/khG1Oaf49FBUkyMBgaAHHuB5+Tr+pnMfaSRXaduxaicbU6h/y1aF82Mdkh4upTCZRw7SNgG2NJN2X0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index; b=auC1Z5HeJb6pzz/T9/0xfJu9NFZm+11/kRia/O8qbOCrleOXgdtMNpVsFY5qC8sa8RWyn13MfB3axyQTOY0+qMT9smKMab+VWGDyTfyLKH63WFIEU2DlNSCjCSycsbioVooSWgMmTAi9wpdOSlZw+uA395HF45m8gJutuhMD/ug= Received: by 10.67.121.15 with SMTP id y15mr1945290ugm.1178200767528; Thu, 03 May 2007 06:59:27 -0700 (PDT) Received: from SCOKARTGXP ( [195.122.110.8]) by mx.google.com with ESMTP id 24sm3389450ugf.2007.05.03.06.59.24; Thu, 03 May 2007 06:59:25 -0700 (PDT) From: "Gilles Scokart" To: Subject: RE: Writing some code after ApacheConEU - Retrieving SNAPSHOT Artifacts Date: Thu, 3 May 2007 16:00:16 +0200 Message-ID: <008501c78d8b$613e6c80$2120a8c0@isabelteam.be> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceNiG3ECvaiGgK1RuOxFUzGqDWOegAAiHTQ X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: Stefan Arentz [mailto:stefan.arentz@gmail.com] > Sent: jeudi 3 mai 2007 15:39 > To: ivy-user@incubator.apache.org > Subject: Re: Writing some code after ApacheConEU - Retrieving SNAPSHOT > Artifacts > > On 5/3/07, Xavier Hanin wrote: > > To distinct things: > > * Ivy do not use maven-metadata.xml files now, and this causes some > > problem, with maven proxy for instance, and maybe also perf, there's > > an issue planned for 2.0 about the proxy thing at least. But Ivy > > supports listing revisions without any specific metadata, so this is > > not really the main problem unless you are using a maven proxy > > Nope, no proxy. What do you mean with 'listing revisions'? > When you don't specify a specific revision, ivy must 'list' all available revision before selecting the right one. That's what it means. Ivy can do this by scanning directories in the repository. > > * we haven't implemented SNAPSHOT yet, but it should be fairly easy to > > get simple case working. Indeed the equivalent in Ivy of SNAPSHOT is a > > + (1.3-SNAPSHOT would be written 1.3-+ in Ivy) Supporting them like > > that is as easy as adding a new VersionMatcher, on the basis of > > SubVersionMatcher. Maybe you could add an issue about that to be sure > > we don't forget to deal with that (there maybe already one, I don't > > remember). > > I'll add that issue. But that is just cosmetics right? If I understand > correctly, the real problem is the maven-metadata.xml. I'll be happy > to add that to Ivy 2.0 if you can give me some pointers to where that > code belongs. > I guess Xavier can give more precise info, but starts by looking at the VersionMatchers, its subclass and its 'caller'. Gilles