Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 76424 invoked from network); 27 Sep 2010 18:03:17 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Sep 2010 18:03:17 -0000 Received: (qmail 23388 invoked by uid 500); 27 Sep 2010 18:03:17 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 23224 invoked by uid 500); 27 Sep 2010 18:03: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 23216 invoked by uid 99); 27 Sep 2010 18:03:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 18:03:16 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dharrigan@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qy0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 18:03:11 +0000 Received: by qyk5 with SMTP id 5so8648716qyk.4 for ; Mon, 27 Sep 2010 11:02:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lYitxOjPNpB7nUJ5tOsCYHkNCf1/UmcXIjTg0TfFavc=; b=YWDQFivBcwY8DF8lMY5RUA+F8QdKVe8IcByq15uPpLW19a4VWcBG1XieuxyNjeu4D+ tR+DrbcRcfhWm5G2R9Ld4MQflnD6SaiL9FwYKPhgDvA6n1sYJ8X6B/NqBXvXwcYNhmqr wZ4w+5mppS+HrOxoevlpUvXZU+gDGdSlJDcRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ZKw5XEgWESJ0rFrei7eHRnrGLiCn8nJBFv2T22MnnMjitwfQOBEky8x3uC3/amJ5cW JwlqmqEljZmAijDFl/tHW5qVxCwTzjNxnShZc15+yLG0Y7a7c5CsZ/amHvg6ko6dhsVB VyRslKGTaDk3ujiZPPZ0fv520VBEayDNyGC/w= MIME-Version: 1.0 Received: by 10.224.3.3 with SMTP id 3mr5843285qal.33.1285610570298; Mon, 27 Sep 2010 11:02:50 -0700 (PDT) Received: by 10.229.188.13 with HTTP; Mon, 27 Sep 2010 11:02:50 -0700 (PDT) In-Reply-To: References: <7E9646C605F85F45B9FEA87EF1F29C123A4ECCB00C@diamondhead.apptechsys.com> Date: Mon, 27 Sep 2010 19:02:50 +0100 Message-ID: Subject: Re: Confusion over latest integration resolution From: David Harrigan To: ivy-user@ant.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, Just out of curiosity, what is the order of your resolvers? Mine is: local shared releases everything else -=3Ddavid=3D- On 27 September 2010 16:45, Steve Miller wrote: > Sounds like you're on the right track for sure. > > As far as resolvers go, I have been using returnFirst=3Dtrue. =A0If I > publish something in my local repo, I always want ivy to use that. > When I'm done developing locally, I clear out my local repo so that > the shared repo is used. It doesn't hurt to do it the way your doing > it, assuming ivy can figure out the latest, but it may decrease > performance of the resolve task. > > Steve > > On Mon, Sep 27, 2010 at 11:39 AM, David Harrigan wr= ote: >> Hi All, >> >> Thanks to everyone who replied :-) >> >> (Yes Steve, it is as you say - after a bit of experimentation I >> understand it now) >> >> I have something working now, this is my setup (btw, using artifactory >> which rocks): >> >> Module A: >> module.version=3D0.1.0-SNAPSHOT >> >> When I build my jar, a fubar.jar is created in my dist directory. When >> I publish to >> artifactory (libs-snaphots-local), it goes in as fubar-0.1.0-SNAPSHOT.ja= r. >> >> Module B: >> In my ivy.xml, I have declared a dependency on fubar as rev=3D"latest.in= tegration" >> which pulls down from artifactory version 0.1.0-SNAPSHOT (or whatever it= is). >> >> Whenever I do a new build of Module A, I keep the version to be 0.1.0-SN= APSHOT, >> but the great thing is when I publish it, the date has changed so when I= ask >> Module B to do a resolve for me, it pulls down the latest from artifacto= ry. >> >> If I now do this: >> >> ant -Dmodule.version=3D0.1.0 ivy.publish.release >> >> Module A goes into the libs-releases-local of artifactory. >> >> Now in my Module B ivy.xml, I change the rev from latest.integration to >> 0.1.0 and when ivy does a resolve in Module B it pulls down the release >> version. >> >> Neato. >> >> I like the fact that I can control the version numbers myself which is g= ood. >> >> I think I understand it now, would I be on the right track? >> >> My last question I have now is local artifacts verses remote artifacts. >> >> Say I am working on Module A. Doing some code changes. I publish >> locally my snapshot (say 0.2.0-SNAPSHOT). In my Module B, I have >> changed the dependency on Module A revision from 0.1.0 now to >> latest.integration. >> >> I remove the value "returnFirst" from my chain and indeed when I do >> a resolve on Module B, ivy installs Module A 0.2.0-SNAPSHOT into >> my Module B libs directory. >> >> My question is this: >> >> Is it correct to leave of returnFirst so that it forces Ivy to examine a= ll >> of the configured resolvers to correctly compare comparisons? >> >> I feel that everything seems to be working well, just looking for some >> assurance that what I've done is accepted good practice and I'm not >> leaving anything out. >> >> Thank you again one and all, it's been a very helpful few hours :-) >> >> -=3Ddavid=3D- >> >> >> On 27 September 2010 14:33, Steve Miller wrote: >>> Actually, the jar will probably be named fubar.jar before you publish >>> it. Then the publish ant task would have a revision of 1.0-SNAPSHOT, >>> so when it's published, the jar would then be fubar-1.0-SNAPSHOT.jar >>> in your repository (depending on your repository pattern). >>> >>> On Mon, Sep 27, 2010 at 7:03 AM, David Harrigan w= rote: >>>> I see, so, if I put something like: >>>> >>>> fubar-1.0-SNAPSHOT.jar >>>> >>>> at the end of my jar and publish that, ivy should (after a bit of >>>> further tweaking) pick up on that? >>>> >>>> I'll give it a whirl later and let you all know. Thanks all for your r= eplies. >>>> >>>> -=3Ddavid=3D- >>>> >>>> On 26 September 2010 16:34, Mitch Gitman wrote: >>>>> This is something I stumbled on myself, but depending on >>>>> "latest.integration" actually resolves a module with a status of inte= gration >>>>> OR GREATER. So, using the default set of statuses, "latest.integratio= n" will >>>>> get the latest module, whether its status is release or milestone or >>>>> integration. >>>>> >>>>> The default status is integration if you don't specify one for ivy:de= liver >>>>> or ivy:publish. The documentation refers to an ivy.status property wh= en it >>>>> comes to how ivy:deliver/ivy:publish defaults the status but doesn't = mention >>>>> what that property's own default value is. There is an ivy.status.def= ault >>>>> property as well. >>>>> >>>>> On Sun, Sep 26, 2010 at 8:01 AM, James Davis = wrote: >>>>> >>>>>> Additionally, the status of the artifact may need to be set to integ= ration. >>>>>> =A0As I understand it, latest integration pulls the latest version o= f an >>>>>> artifact that has a status of integration. =A0However, I am not sure= what the >>>>>> default module status is though (have not looked at the docs to conf= irm). >>>>>> >>>>>> James Davis =95 QA Engineer II/Software Engineer >>>>>> Applied Technical Systems, Inc. =95 Systems Division >>>>>> web: www.atsid.com =95 e-mail: james.davis@atsid.com >>>>>> (p) 360.698.7100 x241 =95 (f) 360.698.7200 >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> I prefer encrypted and signed messages. KeyID: B20A22F9 >>>> Fingerprint: 110A F423 3647 54E2 880F ADAD 1C52 85BF B20A 22F9 >>>> >>> >> >> >> >> -- >> I prefer encrypted and signed messages. KeyID: B20A22F9 >> Fingerprint: 110A F423 3647 54E2 880F ADAD 1C52 85BF B20A 22F9 >> > --=20 I prefer encrypted and signed messages. KeyID: B20A22F9 Fingerprint: 110A F423 3647 54E2 880F ADAD 1C52 85BF B20A 22F9